Red Hat Bugzilla – Bug 149705
Changing name in Node Properties can change Fence Device and Failover Domain names
Last modified: 2015-04-19 20:46:40 EDT
Description of problem:
When editing the "Cluster Node Name" in the Node Properties dialog
box, a user can change the name of a failover domain or a fence device.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Navigate to Node Properties dialog box for cluster node "foo":
Cluster -> Cluster Nodes -> foo -> Edit Node Properties
2. At the Node Properties dialog box, Change "foo" to "foo1".
3. Navigate to failover domain "bar": Cluster -> Managed Resources ->
Failover Domains -> bar
4. At the Node Properties dialog box (opened in step 1), click "OK".
5. Observe the name change of failover domain "foo"; its name changes
from "bar" to "foo1".
6. Observe cluster node name "foo"; its name did *not* change to
For step 5, the failover domain name "bar" was changed to "foo1".
For step 6, the cluster node name "foo" did not change.
The cluster node name "foo" should have been changed to "foo1".
The same results occur with fence device names. That is, in the
preceding "Steps to Reproduce", substituting step 3 with navigating to
a fence device (Cluster -> Fence Devices -> <fence device name>)
results in changing the name of the fence device to "foo1".
As an additional observation to this bug, if you edit an existing fence device
and without clicking OK, click on a node, and then click OK to the edit fence
dialog box, it will CREATE a new fence device rather than edit the one you were
trying to change.
All issues above fixed in 0.9.43
All issues are not fixed. The original case which casued this bug to be opened
still needs to be fixed. Click to edit a node, then without clicking OK,
highlight a fence device, that bug is still there. In fact if you are running in
multicast mode and try that senario, you'll see a trace back:
Traceback (most recent call last):
File "/usr/share/system-config-cluster/ConfigTabController.py", line 900, in
AttributeError: FailoverDomain instance has no attribute 'setInterface'
The additional observation outlined in comment #2 however is fixed.
New and Improved Fix! I didn't understand the subtleties present in the original
ticket...all set in 0.9.44
fix verified in -44.