Bug 197786 - rgmanager ignores restricted="0" directive
Summary: rgmanager ignores restricted="0" directive
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: rgmanager   
(Show other bugs)
Version: 4
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-06 12:39 UTC by Riaan van Niekerk
Modified: 2009-04-16 20:20 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Riaan van Niekerk 2006-07-06 12:39:38 UTC
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 13:34:19 UTC
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.