Bug 826276

Summary:	preupgrade f16 -> f17 selects the wrong kernel, boots using f16 kernel, kaboom
Product:	[Fedora] Fedora	Reporter:	Gilboa Davara <gilboad>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	anaconda-maint-list, dcantrell, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-29 22:18:35 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:

Description Gilboa Davara 2012-05-29 21:57:13 UTC

As the title suggest, I've upgraded a number of i686/x86_64 fully updated VMs from F16 to F17.
After hitting a number of snags that required manual intervention [1] I got pre-upgrade running on all machines.
Once pre-upgrade was complete F17 attempted to boot but blowup on startup (i686) or shutdown (x86_64)
Looking closing it seems that kernel-PAE-3.3.7-1.fc16.i686 was used by anaconda (?) while kernel-PAE-3.3.7-1.fc17.i686 was completely ignored.
Booting into init 1 and removing the offending fc16 kernels (coupled with manual grub2-mkconfig) solved the problem.

- Gilboa

Comment 1 Gilboa Davara 2012-05-29 22:12:48 UTC

(more-or-less solves the problem, I'm getting "file-not-found" errors from grub without additional information [which file], however, in the end F17 on all VM's boots and shuts down just fine)

Comment 2 Jesse Keating 2012-05-29 22:18:35 UTC


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