Red Hat Bugzilla – Bug 175010
clusvcadm does not support locking
Last modified: 2009-04-16 16:18:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Description of problem:
clusvcadm does not support locking of cluster's service managers:
clusvcadm -l (lock services)
clusvcadm -S (display lock status of each service manager)
clusvcadm -u (unlock services)
This feature is important for maintenance and cluster-wide shutdowns. The manpage of clusvcadm does include a reference to the feature (probably left over from the RHEL3 product).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run "clusvcadm -l", "clusvcamd -S", or "clusvcadm -u"
2. Run "man clusvcadm"
Actual Results: feature not implemented
Expected Results: services would become node-locked.
feature was supported in RHEL3 cluster product
*** Bug 175009 has been marked as a duplicate of this bug. ***
Side note - on RHCS3, this only caused locking to occur on the node where it was
run to prevent transitions after node events. The RHCS4 version would be the same.
This is not as simple on RHEL3 because of the forwarding threads -- but I have a
solution mostly done. I'll post a patch after I test on more than one node. ;)
On a second look, I can use VF to write data so that this causes a global
lockdown of services.
Note that this will differ slightly from the RHCS3 implementation: Services
will be prevented from *starting* rather than completely locked in place. So,
after running "clusvcadm -l", you will simply be able to run "service rgmanager
stop" on all nodes and no improper failover events will be triggered.
Note that, like the RHCS3 implementation, nodes (instances of rgmanager, really)
coming online after the lockdown has been issued will be unaware of the
lockdown. Since this feature is only for preventing failover during a total
cluster shutdown, this particular behavior is not worth fixing.
*** Bug 185679 has been marked as a duplicate of this bug. ***
Let me know if this fixes the problem for you!
An advisory 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.