Description of problem: Latest system-config-cluster fail to start. Version-Release number of selected component (if applicable): system-config-cluster 1.0.51-2.0 in RHEL4 (what you get if you up2date to latest everything from RHN). How reproducible: 100% Steps to Reproduce: 1. install system-config-cluster 2. run system-config-cluster 3. observe traceback Actual results: [root@dhcp-1-170 ~]# 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 Expected results: gui comes up Additional info: This is the patch that fixes it [root@dhcp-1-170 ~]# diff -u /usr/share/system-config-cluster/FaildomController.py.bak /usr/share/system-config-cluster/FaildomController.py --- /usr/share/system-config-cluster/FaildomController.py.bak 2007-11-25 10:55:26.000000000 +0000 +++ /usr/share/system-config-cluster/FaildomController.py 2007-11-25 10:55:42.000000000 +0000 @@ -210,7 +210,7 @@ #Set checkboxes for restricted and prioritized val = self.current_faildom.getAttribute("restricted") if val != None: - if val == "Yes" or val == "yes" or val="1": + if val == "Yes" or val == "yes" or val == "1": self.restricted_cbox.set_active(True) else: self.restricted_cbox.set_active(False)
*** Bug 400901 has been marked as a duplicate of this bug. ***
Thanks for the patch - that will sure fix it :( Asking for necessary acks...
ready for z-stream duplo
Absolutely. The patch will do it.
*** Bug 428441 has been marked as a duplicate of this bug. ***
*** Bug 420271 has been marked as a duplicate of this bug. ***
*** Bug 426839 has been marked as a duplicate of this bug. ***
is this ever getting fixed :D
It is all set for an asynchronous update. I will check where it is stuck and give it a kick.
*** Bug 433621 has been marked as a duplicate of this bug. ***
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. http://rhn.redhat.com/errata/RHBA-2008-0792.html