Description of problem: rgmanager restart previously stopped services Version-Release number of selected component (if applicable): rgmanager from cvs HEAD. mostlikely applies to other released branches as well. How reproducible: always Steps to Reproduce: 1. test cluster as described in the wiki 2. start rgmanager all nodes but one 3. stop one service (clusvcadm -s service_128) 4. start rgmanager on the only node that did not start previously Actual results: the service is started again. Expected results: the service should not start as it was previously stopped manually.
Stop = "stop until next transition of (service | rgmanager) then re-evaluate" Typically, rgmanager moves services to this state if a dependency is unsatisfied or restricted-failover domain is offline. Every service state change or node state change triggers an evaluation to see if the service has become runnable. Disable = "stop until administrator intervention" Service is not restarted. Unless re-enabled by an administrator with -e (or the admin did an explicit enable in a RIND event script, which I consider bad form, but is legal) Try - clusvcadm -d instead of clusvcadm -s?
Ok in this case it makes perfect sense and this is not a bug. For some reason I would expect a manual stop to be an alias for disabled or at least this is how i read it via clusvcadm -h Fabio
Created attachment 292188 [details] make help not suck
Moved to upstream cvs