Bug 210482

Summary: RFE: flag for clusvcadm to respect failover domain priorities
Product: [Retired] Red Hat Cluster Suite Reporter: Nils Philippsen <nphilipp>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: adolf.rieger, cluster-maint, hlawatschek, joachim.schneider, michael.hagmann
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0149 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-10 21:18:24 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:
Attachments:
Description Flags
Implements behavior none

Description Nils Philippsen 2006-10-12 14:42:07 UTC 
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:
Comment 1 Lon Hohberger 2006-10-17 14:23:36 UTC 
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.
Comment 2 Nils Philippsen 2006-10-17 15:44:58 UTC 
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?
Comment 3 Lon Hohberger 2006-10-18 16:00:26 UTC 
Yes, please do.
Comment 4 Lon Hohberger 2006-10-18 16:01:13 UTC 
Or we can use this one... *shrug*
Comment 5 Lon Hohberger 2007-01-04 15:46:33 UTC 
Created attachment 144808 [details]
Implements behavior

clusvcadm -Fe <service>
Comment 6 Lon Hohberger 2007-01-04 15:48:31 UTC 
Tested with a service with an ordered failover domain; worked for me.  This
option can not be used with the -[nm] flag.
Comment 7 Lon Hohberger 2007-01-04 15:52:59 UTC 
Patches in CVS
Comment 10 Red Hat Bugzilla 2007-05-10 21:18:24 UTC 
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