Bug 810136 - preupgrade broken with 17 Beta RC3 (17.18): 'no suitable images', 'Unable to process initqueue', '/dev/root does not exist'
Summary: preupgrade broken with 17 Beta RC3 (17.18): 'no suitable images', 'Unable to ...
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F17Beta, F17BetaBlocker
TreeView+ depends on / blocked
Reported: 2012-04-05 09:01 UTC by Adam Williamson
Modified: 2012-05-30 07:11 UTC (History)
8 users (show)

Fixed In Version: anaconda-17.20-1.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-04-05 19:40:27 UTC
Type: Bug

Attachments (Terms of Use)
kickstart and grub config from the attempt (3.21 KB, text/plain)
2012-04-05 09:01 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2012-04-05 09:01:57 UTC
Created attachment 575326 [details]
kickstart and grub config from the attempt

I tried to test preupgrade with anaconda 17.18 (Beta RC3). I downloaded releases.txt and edited it to have baseurl=http://dl.fedoraproject.org/pub/fedora/linux/development/17/x86_64/os/ to force the use of a known up-to-date mirror, after releng had done a compose with the new anaconda/lorax.

After reboot, I got a failure which looks different from the others reported so far, so I think this is with 17.18 :( hard to tell though as it doesn't make it past dracut.

I see these errors at boot:

dracut Warning: no suitable images
dracut Warning: Unable to process initqueue
dracut Warning: /dev/root does not exist

Dropping to debug shell.

At the shell I can see /dev/vda2 is mounted at /run/install/repo . It is the /boot partition of the installed system, I see the /upgrade directory inside it.

cat /proc/cmdline gives:

BOOT_IMAGE=/upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=f9f8667a-5806-41be-a96d-93bbac0334e4:/upgrade/ks.cfg stage2=hd:UUID=f9f8667a-5806-41be-a96d-93bbac0334e4:/upgrade/squashfs.img

I'm attaching the ks.cfg and grub.cfg written by preupgrade prior to reboot. I'm leaving the VM running in the dracut shell in case any more info is desired.

Comment 1 Adam Williamson 2012-04-05 09:02:13 UTC
proposing as Beta blocker. :(

Comment 2 Richard Hughes 2012-04-05 09:52:14 UTC
You know, this feels an awful lot like "whack a mole" as there doesn't seem to be any documented stable anaconda interface for preupgrade to use.

Comment 3 Martin Krizek 2012-04-05 11:02:35 UTC
I reproduced it in KVM x86_64. Anaconda 17.18 (F17 Beta RC3).

Comment 4 eric 2012-04-05 14:50:05 UTC
I, too, am seeing this error trying to upgrade to F17.

Comment 5 Adam Williamson 2012-04-05 19:40:27 UTC
OK, so it turns out that this is simply another case of #810005. Moving discussion there.

Fedora Bugzappers volunteer triage team

*** This bug has been marked as a duplicate of bug 810005 ***

Comment 6 Fedora Update System 2012-04-06 13:58:19 UTC
anaconda-17.19-1.fc17 has been submitted as an update for Fedora 17.

Comment 7 Fedora Update System 2012-04-10 04:14:09 UTC
anaconda-17.20-1.fc17 has been submitted as an update for Fedora 17.

Comment 8 Fedora Update System 2012-04-11 17:22:07 UTC
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.

Comment 9 Tapani Mattila 2012-05-29 19:50:22 UTC
Still there when trying to preupgrade to stable F17.

Comment 10 Adam Williamson 2012-05-30 07:10:36 UTC
No it isn't. There is no general issue with preupgrade at this point. Seeing '/dev/root does not exist' does not mean you are hitting this bug (or any other bug where that error message happens to be mentioned). It's an extremely generic error. Virtually any kind of failure at the dracut stage will wind up showing up as '/dev/root does not exist'.

Comment 11 Adam Williamson 2012-05-30 07:11:50 UTC
To expand - if you're having a problem then the problem you're having is something specific to your particular configuration. It is not this bug, because this bug was a general showstopper which prevented any attempt to use preupgrade, and we have explicitly verified that it no longer exists. I'm not saying you're not hitting a bug. I'm saying you're not hitting _this_ bug. Please file a new one, with a lot more detail about your configuration. Thanks.

Note You need to log in before you can comment on or make changes to this bug.