Bug 872042

Summary: Upgrades on i386 produce a non-bootable system
Product: [Fedora] Fedora Reporter: Tim Flink <tflink>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-01 05:58:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
upgrade output extracted from non-booting system
none
serial console output on boot after upgrade
none
dmesg output from dracut shell after failed reboot
none
debug information requested for dracut issues none

Description Tim Flink 2012-11-01 04:55:12 UTC 
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:
Comment 1 Tim Flink 2012-11-01 04:55:53 UTC 
Created attachment 636458 [details]
upgrade output extracted from non-booting system
Comment 2 Tim Flink 2012-11-01 04:56:24 UTC 
Created attachment 636459 [details]
serial console output on boot after upgrade
Comment 3 Tim Flink 2012-11-01 04:56:51 UTC 
Created attachment 636461 [details]
dmesg output from dracut shell after failed reboot
Comment 4 Tim Flink 2012-11-01 04:57:19 UTC 
Created attachment 636462 [details]
debug information requested for dracut issues
Comment 5 Tim Flink 2012-11-01 05:58:12 UTC 
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.