Bug 154863 - fence mgmt is random which can cause it to not work and backtrace
fence mgmt is random which can cause it to not work and backtrace
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-04-14 12:20 EDT by Corey Marthaler
Modified: 2009-04-16 16:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-04 17:06:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Corey Marthaler 2005-04-14 12:20:47 EDT
Description of problem:
When in the "Fence Configuration" window, sometimes a fence level automagically
pops up and sometimes it does not (i'm not sure what the factor is which causes
the randomocity) and this can cause the fence port definations not to work:

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



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
Comment 1 Corey Marthaler 2005-05-04 17:06:22 EDT
the randomness has since been fixed.

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