Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1122441 - kickstart installation hung when DASD not formatted
Summary: kickstart installation hung when DASD not formatted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2014-07-23 09:18 UTC by Dan Horák
Modified: 2014-07-23 15:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-23 15:17:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dan Horák 2014-07-23 09:18:53 UTC 
I tried a F-20 kickstarted installation yesterday with a freshly allocated DASD which wasn't low-level formatted yet. And the installation was hung with a message in storage.log "..., need dasdmt" (don't remember the exact message)
Comment 1 Dan Horák 2014-07-23 09:23:29 UTC 
so the message was from blivet's dasd_needs_format():

...
log.info("  %s (%s) status is %s, needs dasdfmt", dasd, bypath, status)
Comment 2 Dan Horák 2014-07-23 09:26:57 UTC 
I think bug #1073982 describes the same problem
Comment 3 Samantha N. Bueno 2014-07-23 15:17:54 UTC 
The reason it's freezing in f20 is because there was some cruft in dasd.py that depended upon old code which was scrapped in the UI re-write.

I completely rewrote the dasd code in blivet and anaconda, and the installer now handles cpfmtxa formatted dasds. Those changes unfortunately did not make it into f20, but they are in rhel7.0 and master/f21.

Anyhow, I'm going to close this since it shouldn't be a problem anymore. I have a fix for bug 1073982, which I'll push upstream also.
Note You need to log in before you can comment on or make changes to this bug.