Bug 888234

Summary: Fedora 18 starts with wrong kernel
Product: [Fedora] Fedora Reporter: Matthieu Pupat <redhat_bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: gansalmon, g.kaviyarasu, itamar, jonathan, kernel-maint, madhu.chinakonda, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 905298 (view as bug list) Environment:
Last Closed: 2012-12-18 15:56:59 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 Matthieu Pupat 2012-12-18 10:56:23 UTC 
On my machine I have fedora 17 and fedora 18 BETA installed.

Kernels installed on /boot are 

vmlinuz-3.6.6-3.fc18.x86_64
vmlinuz-3.6.9-2.fc17.x86_64

After installing fedora 18 BETA  system is booted using F18 root partition but fedora 17 kernel (vmlinuz-3.6.9-2.fc17.x86_64)
Comment 1 Chris Lumens 2012-12-18 15:24:43 UTC 
This is likely due to the higher version number of the F17 kernel screwing up the bootloader setup scripts.
Comment 2 Josh Boyer 2012-12-18 15:56:59 UTC 
Yeah, we can't fix this for beta.  Fortunately, booting with the F17 shouldn't be a problem unless you're trying to do secure boot.  If you do a yum update in the F18 partition, it should get a newer kernel than F17.

We're trying to keep the upgrade paths in mind for final release.
Comment 3 Matthieu Pupat 2012-12-18 16:50:44 UTC 
It did boot but I had access to pretty much nothing since the libs were not present (no network for instance). I just modified grub.cfg by hand and could get everything to work and then yum update.