Bug 165140 - Traceback when fencing cluster node and no fence device exists
Summary: Traceback when fencing cluster node and no fence device exists
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster
Version: 4
Hardware: noarch
OS: Linux
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2005-08-04 16:48 UTC by Stanko Kupcevic
Modified: 2009-04-16 20:10 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-10-07 16:50:16 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:753 normal SHIPPED_LIVE system-config-cluster bug update 2005-10-07 04:00:00 UTC

Description Stanko Kupcevic 2005-08-04 16:48:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
Traceback (most recent call last):
  File "/usr/share/system-config-cluster/ConfigTabController.py", line 579, in on_create_fi
  File "/usr/share/system-config-cluster/ConfigTabController.py", line 783, in fi_optionmenu_change
    agent_type = self.fi_agent_hash[self.fi_optionmenu_hash[fi_idx]]
KeyError: -1

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

How reproducible:

Steps to Reproduce:
1. Make sure there are no fence devices configured
2. Try to add a fence to cluster node's fence level

Additional info:

Comment 1 Stanko Kupcevic 2005-08-04 16:53:40 UTC
Fixed in Errata Candidate

Comment 2 Corey Marthaler 2005-09-06 21:46:45 UTC
fix verified in 1.0.15

Comment 3 Red Hat Bugzilla 2005-10-07 16:50:16 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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