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 826529

Summary:	Upgrade from fedora 16->17 with preupgrade keeps using the fc16 kernel.
Product:	[Fedora] Fedora	Reporter:	Martin Tilsted <mt>
Component:	preupgrade	Assignee:	Richard Hughes <hughsient>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	hughsient, mads
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-30 18:54:39 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 Martin Tilsted 2012-05-30 12:32:53 UTC

I upgrade from Fedora16 to Fedora 17 with preupgrade, and anything worked except that the system did not update my /boot/grub2/grub.cfg file at all, so the system booted fedora 17 with the fedora 16 kernel. This does work except that the system does a kernel panic when shutting down.

My system is using raid1 on 2 disks but /boot is not using raid. Mount for /boot is:

/dev/sda2 on /boot type ext2 (rw,relatime,seclabel,user_xattr,acl,barrier=1)

And / (The only other filesystem I have) is mounted as

/dev/md0 on / type ext4 (rw,relatime,seclabel,user_xattr,acl,barrier=1,data=ordered)

A few more details available at http://superuser.com/questions/430293/fedora-17-keeps-using-fedora-16-kernel/430330#430330

Comment 1 Martin Tilsted 2012-05-30 12:34:43 UTC

Doing a grub2-mkconfig -o /boot/grub2/grub.cfg as root fixed the problem. So the system is now using the correct kernel.

Comment 2 Mads Kiilerich 2012-05-30 18:54:39 UTC


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