Description of problem: SSIA, instead of what is specified in /etc/cluster/cluster.conf, "clusvcadm -e <service>" starts <service> on the local node. Version-Release number of selected component (if applicable): rgmanager-1.9.53 How reproducible: Easy Steps to Reproduce: 1. "clusvcadm -e <service>" Actual results: <service> gets started on local node Expected results: <service> should be started on a node in the cluster that satisfies constraints specified in cluster.conf, e.g. priority. Additional info:
Expected behavior. Use the -n <nodename> flag. You can use clusvcadm to explicitly start the service where you want, otherwise, the assumption is that the service should be started locally. The failover domain priority is used for cluster-induced service transitions (which happen after node transitions), and is not used for user-induced enable/disable requests. It may be possible to add a flag to clusvcadm to do this (for 'use failover domain priority, if possible') in a future release, but the current behavior is not a bug. However, the basic behavior for '-e' is correct.
This should be mentioned in "clusvcadm --help" somewhere, the people I've encountered seem to expect "clusvcadm" to respect the constraints in cluster.conf when using "-e". Should I open a new BZ item for an RFE?
Yes, please do.
Or we can use this one... *shrug*
Created attachment 144808 [details] Implements behavior clusvcadm -Fe <service>
Tested with a service with an ordered failover domain; worked for me. This option can not be used with the -[nm] flag.
Patches in CVS
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. http://rhn.redhat.com/errata/RHBA-2007-0149.html