Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 130772 - postinstall depmod should be in GFS-modules package
postinstall depmod should be in GFS-modules package
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gfs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Earl Brassow
GFS Bugs
Depends On:
  Show dependency treegraph
Reported: 2004-08-24 12:12 EDT by Derek Anderson
Modified: 2010-01-11 21:57 EST (History)
0 users

See Also:
Fixed In Version: 6.0.0-15
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-27 13:46:53 EDT
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 Derek Anderson 2004-08-24 12:12:19 EDT
Description of problem:
Version: 6.0.0-10

When GFS was split from a single package to two packages (one for
modules) the postinstall scriptlet for 'depmod -a' remained with the
GFS binaries package.  This no longer does anything to benefit the
user; they need to manually depmod (or reboot) after install since the
install order is GFS, then GFS-modules.  So this postinstall scriptlet
should probably be moved to the GFS-modules package.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Remove all GFS packages
2. Install GFS-6.0.0 package
3. Install GFS-modules-6.0.0 package
4. Run modprobe on a GFS module

Actual results:
modprobe: Can't locate module foo

Expected results:
Module loads.

Additional info:
Comment 1 Derek Anderson 2004-08-24 12:18:12 EDT
*** Bug 130773 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Earl Brassow 2004-08-25 11:16:21 EDT
Should be fixed in GFS-6.0.0-11, which is available in

Comment 4 Derek Anderson 2004-09-27 13:46:53 EDT
Verfified: 6.0.0-15.

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