Bug 60972

Summary:	Upgrade overwrites grub.conf
Product:	[Retired] Red Hat Linux	Reporter:	Kevin - The Alchemist - Sonney <alchemist>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-03-21 16:14:31 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 Kevin - The Alchemist - Sonney 2002-03-11 03:03:42 UTC

Description of Problem:
When performing an upgrade frmo 7.2 -> Hampton B2, grub overwrites the exising
grub.conf with only the data provided in th anaconda session

How Reproducible:
Very. Reproduced on a 7.2 -> Hampton Upgrade, and a fresh install where 2K,
FreeBSD, and a Linux partition shared a grub.conf.  In the latter case, the
FreeBSD was lost, but the 2K (since it was a bootable primary) was retained in
anaconda.

Steps to Reproduce:
Add your own kernel to gurb.conf and do an upgrade. The "user" kernel will be
gone on the post-upgrade reboot.

Additional Information:
The expectation is that my custom settings from the prior install will be
retained, or at least modified, not just blown away in one big swoop. If the rpm
upgrade fo a kernel can do it, why can't anaconda?

Comment 1 Jeremy Katz 2002-03-11 20:09:42 UTC

Because anaconda is rewriting the GRUB config because there's no way to *know*
where to install GRUB.  A lot of these questions were going to get addressed by
new bootloader code that isn't landing with the new Hampton schedule.  I'll see
what I can this week, but this may well end up just being deferred :(

Comment 2 Jeremy Katz 2002-03-13 05:35:10 UTC

Okay, implemented new screens to handle this today.  I would appreciate testing
of this as much as possible during the next beta.