Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 147640 - Install of GFS-modules package doesn't update module dependencies
Install of GFS-modules package doesn't update module dependencies
Status: CLOSED DUPLICATE of bug 148001
Product: Red Hat Cluster Suite
Classification: Retired
Component: gfs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Feist
GFS Bugs
Depends On:
  Show dependency treegraph
Reported: 2005-02-09 18:46 EST by Mike MacCana
Modified: 2010-01-11 22:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-10 10:40:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike MacCana 2005-02-09 18:46:56 EST
Description of problem:
%post for GFS-modules doesn't update the module dependencies. If it did,
customers would be able to skip a step when adding new nodes to their clusters.
It'd also avoid a minor annoyance.

Version-Release number of selected component (if applicable):
Comment 1 Ken Preslan 2005-02-09 19:02:48 EST
Reassign to package maintainer
Comment 2 Derek Anderson 2005-02-10 10:40:36 EST
Setting to version 3 and closing as not a bug.  More recent versions of 
GFS-modules have fixed this issue. 
# rpm -qp --scripts GFS-modules-6.0.2-25.x86_64.rpm 
postinstall scriptlet (using /bin/sh): 
depmod -a 
Comment 3 Adam "mantis" Manthei 2005-02-14 14:10:59 EST
Actually... this is a bug.  "depmod -a" only works for the currently running
kernel.  It doesn't work when installing GFS on to a system that is not booted
into the kernel that GFS is going to run.  For example, it won't work if you are
running kernel version 2.4.21-15 and you install GFS modules that are for kernel
version 2.4.21-27.0.1. This bug is a dup of bug #148001, marking it as such.

*** This bug has been marked as a duplicate of 148001 ***

Note You need to log in before you can comment on or make changes to this bug.