Bug 833347

Summary: cpglockd init script is not added to chkconfig db
Product: Red Hat Enterprise Linux 6 Reporter: Fabio Massimo Di Nitto <fdinitto>
Component: rgmanagerAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.4CC: cluster-maint, mjuricek
Target Milestone: rcKeywords: EasyFix
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rgmanager-3.0.12.1-14.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 10:18:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fabio Massimo Di Nitto 2012-06-19 09:31:34 UTC
Description of problem:

rgmanager spec file is missing a couple of bits related to cpglockd handling.

Specifically:

%post
/sbin/chkconfig --add rgmanager

the post section should add:
/sbin/chkconfig --add cpglockd

otherwise chkconfig --list does not show cpglockd.

----

%preun
if [ "$1" = 0 ]; then
        /sbin/service rgmanager stop >/dev/null 2>&1
        /sbin/chkconfig --del rgmanager
fi

once rgmanager is stopped and removed at uninstall time, the same should be done for cpglockd.

both issues are minor.

Comment 1 RHEL Program Management 2012-07-10 05:51:11 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 RHEL Program Management 2012-07-11 01:49:40 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 8 errata-xmlrpc 2013-02-21 10:18:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0409.html