Bug 145458

Summary: lock_gulmd initscript should run only in gulm configuration
Product: [Retired] Red Hat Cluster Suite Reporter: Adam "mantis" Manthei <amanthei>
Component: gulmAssignee: Adam "mantis" Manthei <amanthei>
Status: CLOSED NEXTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-09 21:11:17 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:
Bug Depends On:    
Bug Blocks: 144795    

Description Adam "mantis" Manthei 2005-01-18 17:34:09 UTC
Description of problem:
The gulm initscript should run only if a gulm configuration is
detected.  The script will need to check /etc/cluster/cluster.conf to
determine if gulm is configured since ccsd will not be in a quorate
state when this script is started on bootup.  The check should
silently cause the initscript to exit so that users are not alarmed by
unneccessary error messages.

Version-Release number of selected component (if applicable):
problem exits in  gulm-1.0-0.pre11.0 and earlier.

Comment 1 Adam "mantis" Manthei 2005-01-20 17:58:28 UTC
diff -u -p -r1.1.2.4 lock_gulmd
--- cluster-RHEL4/gulm/init.d/lock_gulmd        12 Jan 2005 16:00:26
-0000      1.1.2.4
+++ cluster-RHEL4/gulm/init.d/lock_gulmd        20 Jan 2005 17:55:34 -0000
@@ -36,6 +36,21 @@ then
        GULM_OPTS="$GULM_OPTS --use_ccs"
 fi
 
+
+# If gulm is using ccs, then make sure that there is a gulm
+# section in /etc/cluster/cluster.conf, otherwise abort.
+# FIXME -- Should this be silent?  I think users should get some
+#          feedback, but others might not want added verbosity to
+#          the boot process.  Oh well... it's only one line :)
+if echo "$GULM_OPTS" | grep -qE "(--use_ccs|[\t ]-[VhCed]*c)" 
+then
+       if ! grep -qE "<[\t ]*gulm[\t ]*.*>" /etc/cluster/cluster.conf 
+       then
+               echo "lock_gulmd: no <gulm> section detected in
/etc/cluster/cluster.conf"
+               exit 11
+       fi
+fi
+



/cvs/cluster/cluster/gulm/init.d/lock_gulmd,v  <--  lock_gulmd
new revision: 1.5; previous revision: 1.4

/cvs/cluster/cluster/gulm/init.d/lock_gulmd,v  <--  lock_gulmd
new revision: 1.1.2.5; previous revision: 1.1.2.4


Comment 2 Derek Anderson 2005-02-09 21:11:17 UTC
Verified in gulm-1.0-0.pre16.0.

Starting lock_gulmd:  no <gulm> section detected in 
etc/cluster/cluster.conf [FAILED]