Bug 463983
| Summary: | gfs2-kmod package should no longer override the in kernel gfs2 module | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Chris Feist <cfeist> |
| Component: | kernel | Assignee: | Chris Feist <cfeist> |
| Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.3 | CC: | atodorov, bkahn, cluster-maint, cmarthal, ddomingo, edamato, syeghiay |
| Target Milestone: | beta | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-15 20:16:00 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
Chris Feist
2008-09-25 19:15:54 UTC
Just a note, if this bug is not fixed then when the user installs the latest kernel with a new gfs2 module, it will not be used if they have any old gfs2-kmod packages installed. This fix is built in gfs2-kmod-1.116-1.12.el5. We need a release note to document that installing the new gfs2-kmod will disable the external gfs2-kmod module on older kernels. Doing yum update leads to: Transaction Check Error: file /etc/depmod.d/gfs2.conf from install of kmod-gfs2-xen-1.116-1.14.el5 conflicts with file from package kmod-gfs2-xen-1.92-1.1.el5 file /etc/depmod.d/gfs2.conf from install of kmod-gfs2-xen-1.116-1.14.el5 conflicts with file from package kmod-gfs2-1.92-1.1.el5 file /etc/depmod.d/gfs2.conf from install of kmod-gfs2-1.116-1.14.el5 conflicts with file from package kmod-gfs2-xen-1.92-1.1.el5 file /etc/depmod.d/gfs2.conf from install of kmod-gfs2-1.116-1.14.el5 conflicts with file from package kmod-gfs2-1.92-1.1.el5 Is this supposed to be fixed or is desired behavior? Please advise. Do we need separate bz for that? Thanks, Alexander. Filed comment #6 as bug #467013 Marking this a DUP of 486883 because I think the beset way to fix this problem is by having an Obsoletes in the kernel. *** This bug has been marked as a duplicate of bug 465883 *** |