Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 62216

Summary:	kernel-bigmem not selected for upgrade from 7.2's kernel-enterprise
Product:	[Retired] Red Hat Public Beta	Reporter:	Stephen Tweedie <sct>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	skipjack-beta1	CC:	sct
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-28 21:45:23 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:
Bug Depends On:
Bug Blocks:	61590

Description Stephen Tweedie 2002-03-28 15:01:02 UTC

Description of Problem:
On a large (8Gb) machine running 7.2 with kernel-enterprise and kernel-smp
kernels involved, a Skipjack upgrade selects only kernel-smp as the upgrade
kernel.  In fact, kernel-bigmem should be the kernel used for the upgrade, as
that supercedes the old kernel-enterprise package and is required for >4Gb
memory support.

Version-Release number of selected component (if applicable):
Install media from skipjack public beta 1.

How Reproducible:
100%

Steps to Reproduce:
1. Install 7.2 with kernel-enterprise on a large memory machine
2. upgrade to Skipjack

Actual Results:
kernel-smp is selected by the installer for the upgrade.

Expected Results:
kernel-bigmem should be selected by the installer for the upgrade.

Additional Information:

Comment 1 Jeremy Katz 2002-03-28 19:46:01 UTC

That's because kernel-bigmem didn't obsolete/provide kernel-enterprise so there
was no way for anaconda to know the two were related.  Current CVS kernel has
kernel-bigmem obsoleting kernel-enterprise which will fix this.

Comment 2 Jay Turner 2002-04-02 19:03:17 UTC

Indeed, fix confirmed with 2.4.18-0.13.