Bug 130773 - postinstall depmod should be in GFS-modules package
Summary: postinstall depmod should be in GFS-modules package
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gfs (Show other bugs)
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Kiersten (Kerri) Anderson
QA Contact: GFS Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-24 16:17 UTC by Derek Anderson
Modified: 2010-01-12 02:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-29 20:00:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:490 normal SHIPPED_LIVE Updated GFS packages 2004-09-29 04:00:00 UTC

Description Derek Anderson 2004-08-24 16:17:01 UTC
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 16:18:05 UTC

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

Comment 2 David Lawrence 2004-09-29 20:00:45 UTC
An errata 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.


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