Bug 808499
| Summary: | dracut: FATAL: Don't know how to handle 'root=anaconda-kickstart' | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Krizek <mkrizek> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | anaconda-maint-list, awilliam, cjashfor, Danzisso, elreydetodo, g.kaviyarasu, hoyang, hughsient, jaroslav.pulchart, jonathan, mvanross, nathanael, nneul, peter, robatino, vanmeeuwen+fedora, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | anaconda-17.20-1.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-06 04:29:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 752649 | ||
|
Description
Martin Krizek
2012-03-30 14:39:20 UTC
Proposing as Beta blocker per criterion: "The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria". Discussed during 2012-03-30 blocker review meeting. Accepted as blocker per criterion cited in comment #1. I tested and reproduced this. bcl thinks it's due to "the kickstart parsing rewriting root=". Seems a good supposition, because there is no root= in the cmdline written by preupgrade, it is: linux /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=blahblah:/upgrade/ks.cfg stage2=hd:UUID=blahblah:/upgrade/squashfs.img initrd /upgrade/initrd.img note that there's no UUID= in the 'repo=' parameter. There are two colons, indicating something was maybe supposed to go between them. Seems like that may be a bug somewhere. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Discussed at 2012-03-30 blocker review meeting. Accepted as a blocker per criterion cited in comment #1. We need to determine if the bug here is in preupgrade or anaconda to know whether we should block the RC3 compose for it; if anyone is prepared to decide that, please let us know :) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers for now, bcl says anaconda. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers "hd::".. is a special preupgrade-only notation for "the disk device we're upgrading from", so that's legit. Digging deeper now. Actually this turns out to be pretty straightforward: we didn't support stage2= like we used to. Patches will be along soon. anaconda-17.17-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.17-1.fc17 reproduced with F17 Beta RC3 Not reproduced here, but I hit another failure. https://bugzilla.redhat.com/show_bug.cgi?id=810136 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Same here, this one seems to be fixed, but I hit #810136. Package anaconda-17.17-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.17-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-5388/anaconda-17.17-1.fc17 then log in and leave karma (feedback). When should this be available in preupgrade from fc16? OK, further testing verifies that this is resolved, and the remaining bugs are 810005 and 810136. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers anaconda-17.19-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.19-1.fc17 anaconda-17.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.20-1.fc17 anaconda-17.20-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |