Red Hat Bugzilla – Bug 468433
Installing Cluster Storage group makes xen the default kernel
Last modified: 2018-10-19 22:54:33 EDT
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.
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.
I went back and reinstall RHEL5.2 with and without Cluster Storage and both come up with only the regular kernel.
(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
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.
*** Bug 466336 has been marked as a duplicate of this bug. ***
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>
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.
Change checked into distill
Verified fixed in RHEL5.3-Server-20081029.0.
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