Bug 241412

dlehman - this should be pretty simple.  We can just add some more packages to
the list of what gets selected by default for certain installation keys, correct?

Here's a snippet from the ClusterStorage comps file:

      <packagereq type="default">kmod-gfs</packagereq>
      <packagereq type="default">kmod-gfs-kdump</packagereq>
      <packagereq type="default">kmod-gnbd</packagereq>
      <packagereq type="default">kmod-gnbd-kdump</packagereq>
      <packagereq type="default">lvm2-cluster</packagereq>
      <packagereq type="optional">kmod-gfs-PAE</packagereq>
      <packagereq type="optional">kmod-gfs-xen</packagereq>
      <packagereq type="optional">kmod-gnbd-PAE</packagereq>
      <packagereq type="optional">kmod-gnbd-xen</packagereq>

So what you are asking is that the PAE/xen subpackages be installed, but only in
the event that the corresponding kernel-PAE/kernel-xen is selected. Is this correct?

If we're going to do this, we should really do it more generically in case we
add more kmods in the future.  There's already a yum plugin that is supposed to
do the right thing, so we might be able to just include it, enable plugin use
and go from there.

re: comment #3, not sure why it would be just PAE.  What's needed is that
whenever the Advanced Platform is selected, the XEN & non-XEN kernel modules for
GFS and GNBD should be installed.  What I've seen is that an AP install does not
install kmod-gfs-xen.  This is true on x64 boxes too, not just PAE.

Is the solution here to change the type="default" for the kmod-gfs-{xen,PAE}
packages?

My concern is that setting them to "default" might pull in kernel-xen and
kernel-PAE if they're not already selected, which doesn't sound desirable.

dlehman: what are your thoughts here?  What's the yum plugin katzj metions in
comment#4 that might solve this in a generic way?

For some reason I feel like I've answered this question before at some point, but...

There's a subpackage of yum-utils called yum-fedorakmod, which contains a plugin
to manage exactly this sort of thing. We don't ship that in RHEL, but it's just
one python file. I rigged an updates.img to use the plugin and it solved this
particular problem. Now I just need to figure out how best to get it into the tree.

And isn't there something special that'll need to happen to get this into 5.1 at
this point?

Spoke a bit further on this w/ dlehman (thanks Dave!)

Adding QA_ACK for 5.1 to add yum-fedorakmod support into the installer so that
it pulls in the proper kmod packages when a matching kernel is installed.

Should adding/packaging yum-fedorakmod for post-install be needed, we will track
that in a separate bz.

Confirmed fixed in snap#7 and snap#8 by rkeena.

Actually confirmed by rkenna (1 'e', 2 'n's)  :)
But, yes, this is working properly now.

Doh! sorry Rob, thanks for the info :)

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

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 the 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/RHBA-2007-0644.html