Bug 197786 - rgmanager ignores restricted="0" directive
rgmanager ignores restricted="0" directive
Status: CLOSED NOTABUG
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-06 08:39 EDT by Riaan van Niekerk
Modified: 2009-04-16 16:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-06 09:34:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Riaan van Niekerk 2006-07-06 08:39:38 EDT
Description of problem:

When I create an unrestricted, unordered failover domain, the service relocates
to the member of the failover domain as soon as the member rejoins the cluster.

Version-Release number of selected component (if applicable):
rgmanager-1.9.46-0

How reproducible:
every time

Steps to Reproduce:
1. configure service with unrestricted, unordered failover domain.
node 1 is member of failover domain. node 2 is not
2. service rgmanager stop
3. service relocates from node 1 to node 2
3. service rgmanager start
  
Actual results:

service relocates from node 2 to node 1

Expected results:

service does not relocate to node 1 but stays on node 2
Comment 1 Riaan van Niekerk 2006-07-06 09:34:19 EDT
I am closing this bugreport. I reread http://people.redhat.com/lhh/fd.html and
it seems this is how it should work. I have logged a support incident. If
necessary, I will log an RFE.

Note You need to log in before you can comment on or make changes to this bug.