Description of problem: This is related to 154863 If I have a Fence-Level-1 show up and I click "Add..." again, it will cause a backtrace: Traceback (most recent call last): File "/usr/share/system-config-cluster/ConfigTabController.py", line 603, in on_create_level obj = model.get_value(iter, FENCE_OBJ_COL) #node TypeError: iter must be a GtkTreeIter Version-Release number of selected component (if applicable): [root@tank-03 ~]# rpm -qa | grep system-config-cluster system-config-cluster-0.9.30-1.0
this back trace can also occur when clicking on "add a new fence...": Traceback (most recent call last): File "/usr/share/system-config-cluster/ConfigTabController.py", line 566, in on_fi_ok type = model.get_value(iter,FENCE_TYPE_COL) TypeError: iter must be a GtkTreeIter
Both cases are now handled in 0.9.36-1.0 Levels can be added now without a tree selection If create fence button is clicked with no level selected, the user is first prompted to select a level.
The backtrace is now gone so I'll close this bug, however, something still needs to be done to make fence mgmt more intuitive and this is addressed in 156109. Now if I continue to click the "Add a New Fence Level" I just see more meaningless "levels" show up and as a user I don't know what to do with them.