Description of problem: When I upgrade an updated (using updates, not updates-testing) F17 install in an i386 VM, the fedup process appears to complete but the resultant system is not able to boot (gets to the mount phase of dracut). There are a lot of ignored transaction errors in upgrade.out but I'm not sure if those are related Version-Release number of selected component (if applicable): fedup-dracut (888d05d5393c38538b3d41cb5b36b62d9e315bd2 from github) fedup (1b6992b85ebb1fe7bb1b00659b24d9f3ad2173eb from github) How reproducible: I've been able to reproduce this 3 times in a row on a VM, resetting the VM every time Steps to Reproduce: 1. upgrade using latest fedup from git, built for i386 2. reboot after upgrade is complete 3. Actual results: System does not boot, fails pre-pivot Expected results: System boots into a working F18 installation Additional info:
Created attachment 636458 [details] upgrade output extracted from non-booting system
Created attachment 636459 [details] serial console output on boot after upgrade
Created attachment 636461 [details] dmesg output from dracut shell after failed reboot
Created attachment 636462 [details] debug information requested for dracut issues
Chalk this one up to user error. I figured out that I was pointing the i386 fedup-cli at an x86_64 repo mirror. The upgrade process completed but the resultant system didn't boot - couldn't imagine why. When I do an i386 upgrade using an _i386_ F18 mirror, the upgrade works.