Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 468433

Summary: Installing Cluster Storage group makes xen the default kernel
Product: Red Hat Enterprise Linux 5 Reporter: Nate Straz <nstraz>
Component: compsAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: adaora.onyia, cfeist, dgregor, dlehman, nstraz, rick.hester, rwilliam, syeghiay, tao
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:19:09 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 Nate Straz 2008-10-24 18:09:34 UTC
Description of problem:

After installing RHEL5.3-Server-20081020.1 I found that the default kernel was 
2.6.18-120.el5xen instead of 2.6.18-120.el5 on my x86_64 system.  
My kickstart.cfg includes the Cluster Storage group but not the Virtualization group.

Version-Release number of selected component (if applicable):
tree RHEL5.3-Server-20081020.1

How reproducible:
100%

Steps to Reproduce:
1. Add "@Cluster Storage" to the %packages section of your kickstart.cfg
2. install
3. check `uname -r`
  
Actual results:
A dom0 is started

Expected results:
Regular kernel should be installed

Additional info:
The main clue that this happened was that I could not login using the serial console anymore.

Comment 1 Chris Lumens 2008-10-24 18:18:55 UTC
From the ClusterStorage repo's comps file:

      <packagereq type="default">kmod-cmirror</packagereq>
      <packagereq type="default">kmod-cmirror-PAE</packagereq>
      <packagereq type="default">kmod-cmirror-xen</packagereq>

I bet what's happening here is that by selecting this group, you are
automatically getting all those packages selected for installation (because
they're default).  Then kmod-cmirror-xen requires the Xen kernel of course,
which pulls that package in, and then you're stuck.

Seems like we're hitting a lot of issues like this right now.  I wonder if
there have been changes to the comps files recently.

Comment 2 Nate Straz 2008-10-24 18:31:25 UTC
I went back and reinstall RHEL5.2 with and without Cluster Storage and both come up with only the regular kernel.

Comment 3 Jeremy Katz 2008-10-24 18:37:25 UTC
(In reply to comment #1)
> Seems like we're hitting a lot of issues like this right now.  I wonder if
> there have been changes to the comps files recently.

revision 1.24
date: 2008/09/23 14:54:33;  author: dgregor;  state: Exp;  lines: +2 -0
added kmod-cmirror-PAE and kmod-cmirror-xen

Comment 4 David Lehman 2008-10-24 19:07:53 UTC
The problem is that kmod-cmirror-xen is marked as selected by default in the comps file. This pulls in kernel-xen as a dependency. So when the time comes to make sure we have a kernel installed we see that kernel-xen is already selected and therefore do not auto-select the regular kernel. We include the kmod yum plugin to handle the -xen (or PAE or whatever else) variants of kmod packages -- only generic kmod packages should be marked as default.

Comment 5 David Lehman 2008-10-24 19:08:40 UTC
*** Bug 466336 has been marked as a duplicate of this bug. ***

Comment 7 Dennis Gregorovic 2008-10-24 19:16:47 UTC
I can make those packages optional.  Just to clarify, should all of the following be optional in that group?

      <packagereq type="default">kmod-cmirror</packagereq>
      <packagereq type="default">kmod-cmirror-PAE</packagereq>
      <packagereq type="default">kmod-cmirror-xen</packagereq>

Comment 8 David Lehman 2008-10-24 19:25:24 UTC
They don't need to be optional -- in that case they won't get installed and we'll have another bug.

Leave the kmod-cmirror as default and remove the other two completely (kmod-cmirror-xen, kmod-cmirror-PAE). Let yum's kmod plugin deal with kernel variants and associated kmod package selection.

Comment 9 Dennis Gregorovic 2008-10-24 19:38:18 UTC
Change checked into distill

Comment 11 Nate Straz 2008-10-30 22:10:58 UTC
Verified fixed in RHEL5.3-Server-20081029.0.

Comment 14 errata-xmlrpc 2009-01-20 21:19:09 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-0133.html