Red Hat Bugzilla – Bug 149508
Navigation tree expands unexpectedly
Last modified: 2015-04-19 20:46:40 EDT
Description of problem:
Starting from a collapsed gross navigation tree, navigating to a
properties dialog box or a delete dialog box, opening and closing the
dialog box with "OK", "Yes", or "Close" cause the gross navigation
tree to fully expand. The circumstances under which that behavior
occurs is described in more detail in "Steps to Reproduce".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Collapse gross navigation tree by clicking triangle icon at
2. Click triangle icon at "Cluster" again to expand navigation tree,
exposing the major elements: Cluster Nodes, Fence Devices, and
3. Navigate to any of the following dialog boxes and close the box as
Dialog Box Close Method
Node Properties Click OK
Delete Node -> Warning Click Yes
Fence Device Configuration Click OK
Delete Fence Device -> Warning Click Yes
Failover Domain Configuration Click Close
Delete Failover Domain -> Warning Click Yes
For example, to demonstrate the action at the Node Properties
dialog box, navigate as follows: Cluster Nodes -> Add Node
Properties. At the Node Properties dialog box, enter node name at
the "Cluster Node Name" text box and click OK.
Gross navigation tree expands fully.
Gross navigation tree expected to remain as it was before closing
This was a complicated fix! Much more involved than immediately thought.
Fixed in 0.9.17-1.0
Now only the tree which was changed expands. So if you close the nodes section,
and then add a new node, that tree expands when it should stay the way it was.
The user can open it if they want.
Actually, I did this purposefully so that the user would have immediate feedback
that the node they had added was present in the config. Leaving that section
closed would not provide any immediate evidence that the operation was
usccessful. If, after reading this explanation, you still feel it should
remain closed, then please reset this bug to assigned again. :)
We still really think that if the user went to the trouble to close the tree
then it should stay that way. They could have left it open when creating the new
node or opened it afterwards if they want feed back.
This late in the game I'll close it deferred and argue again for it in the uber