Bug 506216

Summary:	grubby needs to respect default kernel on remove
Product:	Red Hat Enterprise Linux 5	Reporter:	Bill McGonigle <bill-bugzilla.redhat.com>
Component:	mkinitrd	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.3	CC:	atodorov, ddumas
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-10 17:35:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill McGonigle 2009-06-16 04:11:58 UTC

Description of problem:

  grubby doesn't set default= based on kernel in /etc/sysconfig/kernel when a kernel is removed

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

  mkinitrd-5.1.19.6-44.i386

How reproducible:
 
  always

Steps to Reproduce:
1. have two flavors of kernel installed, e.g. kernel and kernel-xen
2. set the default kernel type to kernel-xen
3. make sure it's the default kernel
4. yum install a newer kernel-xen (grubby updates, new kernel-xen is now default)
5. yum remove that newer kernel-xen
  
Actual results:
  
  plain kernel is now the default (default=0)

Expected results:

  previously default kernel-xen is the default

Comment 1 Bill McGonigle 2009-06-16 04:15:17 UTC

(or, in step 4, rpm install a newer kernel-xen)

Comment 2 David Cantrell 2010-07-02 03:01:39 UTC

grubby has always worked this way.

Comment 3 RHEL Program Management 2010-07-02 03:05:00 UTC

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 4 Bill McGonigle 2010-07-02 03:26:06 UTC

Sure, why not?  "It's always been broken" seems like a poor reason to close a bug.