Bug 158415 - Cannot add failover domain to service
Cannot add failover domain to service
Status: CLOSED NEXTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-21 23:55 EDT by Henry Harris
Modified: 2009-04-16 16:09 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-31 11:33:13 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 Henry Harris 2005-05-21 23:55:04 EDT
Description of problem:  I was able to create a failover domain with the GUI but
after assigning a failover domain to a service it was not retained and did not
show up in the services section of the cluster.conf file although it was in the
failover domain section.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jim Parsons 2005-05-24 10:04:26 EDT
This is fixed in 0.9.56-1.0
Comment 2 Corey Marthaler 2005-05-25 11:09:22 EDT
fix verified in -60.
Comment 3 Lon Hohberger 2005-05-26 14:40:41 EDT
I reproduced this with -64 on red

- Ssh'd in with -Y
- Created new "testdomainthing" service.

Try 1:
- clicked testdomainthing
- clicked edit service properties
- selected a failover domain from the dropdown
- clicked close
- clicked testdomainthing service
- clicked edit service properties
- Failover domain...: "None" :(


Try 2:
- clicked testdomainthing
- clicked edit service properties
- selected a failover domain from the dropdown
- clicked close
- file->save
- quite system-config-cluster
- look at /etc/cluster/cluster.conf -- no domain for the service.


This *works* if I change the domain a service is bound to.  That is, if the
service has a domain already, then you can switch it to another domain and the
configuration reflects this correctly.
Comment 4 Jim Parsons 2005-05-27 13:52:13 EDT
Yes - found the error. Fixed in 0.9.66-1.0
Comment 5 Lon Hohberger 2005-05-27 14:52:59 EDT
Both test cases I mentioned previously work properly now.
Comment 6 Corey Marthaler 2005-05-31 11:33:13 EDT
per Lon's comment, marking fixed.

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