Bug 433621

Summary: Error in system-config-cluster tool
Product: [Retired] Red Hat Cluster Suite Reporter: Juan Ramon Martin <jrmartin>
Component: redhat-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 4CC: cluster-maint, edamato
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-23 13:34:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Juan Ramon Martin 2008-02-20 12:28:18 UTC
Description of problem:
When updating system-config-cluster to system-config-cluster-1.0.51-2.0 the
program does not start giving the following error:
~]# system-config-cluster
Traceback (most recent call last):
  File "/usr/sbin/system-config-cluster", line 52, in ?
    from ConfigTab import ConfigTab
  File "/usr/share/system-config-cluster/ConfigTab.py", line 27, in ?
    from ConfigTabController import ConfigTabController
  File "/usr/share/system-config-cluster/ConfigTabController.py", line 35, in ?
    from FaildomController import FaildomController
  File "/usr/share/system-config-cluster/FaildomController.py", line 213
    if val == "Yes" or val == "yes" or val="1":
                                          ^
SyntaxError: invalid syntax


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

How reproducible:
Upgrade to version 1.0.51-2.0 and execute system-config-cluster


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
To correct it, the only thing that must be done is substitute val="1" by
val=="1" on file
"/usr/share/system-config-cluster/FaildomController.py", line 213

Comment 1 Jim Parsons 2008-04-23 13:34:25 UTC
This has been fixed in a z-stream release.

*** This bug has been marked as a duplicate of 398291 ***