Bug 912320

Summary:	Fedora kernel updates after fedup is used fail due to incorrect command line parameters
Product:	[Fedora] Fedora	Reporter:	Brian Morrison <bdm>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	contact, rmancy, tflink, wwoods
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:	2013-10-09 19:42:01 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 Brian Morrison 2013-02-18 12:08:13 UTC

Description of problem:

After running fedup, F17 kernel updates pick up command line from the Upgrade entry in /etc/grub2.cfg instead of using the working command line from the existing kernel boot entries


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

fedup-0.7.2-1.fc17


How reproducible:

Always if System Upgrade entry is the first entry in /etc/grub2.cfg and a new F17 kernel comes from updates repo

Steps to Reproduce:
1. Run fedup with normal upgrade-to-F18 options on command line
2. Install an updated F17 kernel using yum update
3. Reboot system and select upgraded kernel not system upgrade
  
Actual results:

New kernel gets the wrong command line parameters and cannot boot, resulting in a boot loop.

Expected results:

Upgrade choice should be the last entry in /etc/grub2.cfg so that a bootable kernel is always used when yum updates a kernel before the system upgrade is run.

Additional info:

Comment 1 Aissen 2013-04-29 10:57:51 UTC

I have the same problem with fedup from F18 to F19.

Comment 2 Fedora End Of Life 2013-07-04 04:23:20 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Aissen 2013-07-04 08:05:03 UTC

This also affects the transition from F18 to F19.

Comment 4 Brian Morrison 2013-07-04 10:24:11 UTC

Changing version to F18 as it still affects all versions I've tried so far.

Comment 5 Will Woods 2013-10-09 19:28:51 UTC

*** Bug 918894 has been marked as a duplicate of this bug. ***

Comment 6 Will Woods 2013-10-09 19:42:01 UTC


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