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 825092

Summary: Fedora 17 DVD upgrade delivers an unusable system
Product: [Fedora] Fedora Reporter: Panos Kavalagios <Panos.Kavalagios>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: anaconda-maint-list, dcantrell, g.kaviyarasu, jonathan, jones.peter.busi, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-25 19:21:20 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
Old F16 kernel is loaded after upgrade
none
Plymouth text graphics still advertise Fedora 16
none
The system hangs at this screen when boot is over
none
Shutdown or reboot cause a kernel panic
none
Contents of /var/log/anaconda none

Description Panos Kavalagios 2012-05-25 05:47:41 UTC 
Description of problem: Multiple problems have been identified after a successfully DVD upgrade of Fedora 16 to Fedora 17 using Fedora 17 Beta DVD installation media Fedora-17-Beta-i386-DVD.iso.


Version-Release number of selected component (if applicable): anaconda F17 beta


How reproducible: Upgrade your Fedora 16 with the DVD option


Steps to Reproduce:
1. DVD boots OK and it selects to upgrade you F16
2. After installation is over, you are prompted to reboot
3. Press the reboot button
  
Actual results: The new system boots the old F16 kernel (fedora17-dvd-upgrade-kernel.png), the booting process when stopped (fedora17-dvd-upgrade-startup.png) it does not provide you any way to log in. No graphical KDM is available (OK for that you need guest additions probably), but neither text login propmpt. Pressing Alt-F2 does not switch to any virtual console.


Expected results: You should be able to log in to the system at least in a text console.


Additional info: If you try to issue a shutdown signal or a ctrl-alt-del sequence, the upgraded system produces a kernel panic (fedora17-dvd-upgrade-panic.png). Plymouth text graphics continue to advertise the system as Fedora 16 (fedora17-dvd-upgrade-plymouth.png).
Comment 1 Panos Kavalagios 2012-05-25 05:49:25 UTC 
Created attachment 586759 [details]
Old F16 kernel is loaded after upgrade
Comment 2 Panos Kavalagios 2012-05-25 05:50:47 UTC 
Created attachment 586760 [details]
Plymouth text graphics still advertise Fedora 16
Comment 3 Panos Kavalagios 2012-05-25 05:52:31 UTC 
Created attachment 586761 [details]
The system hangs at this screen when boot is over

There is no way to log in to the system. Neither graphical nor text. The login prompt is vanished.
Comment 4 Panos Kavalagios 2012-05-25 05:53:57 UTC 
Created attachment 586762 [details]
Shutdown or reboot cause a kernel panic

A three-finger salutation (ctrl-alt-del) or shutdown signal causes the system to emit a kernel exception.
Comment 5 Panos Kavalagios 2012-05-25 06:11:57 UTC 
Created attachment 586764 [details]
Contents of /var/log/anaconda

Hopefully, I was able to boot in single user mode. In the attached zip archive anaconda.zip you may find /var/log/anaconda logs for further investigation. I haven't noticed any problem in the logs and the only weird things is that the system reports no F17 PAE kernel installed (rpm -qa). Either F17 is shipped with no kernel (unlikely scenario :)) or anaconda didn't force a kernel upgrade.
Comment 6 Jesse Keating 2012-05-25 19:21:20 UTC 

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