Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: ccs is used to parse an invalid cluster.conf file
Consequence: ccs issues a traceback
Fix: ccs now checks to see if the cluster.conf is invalid
Result: If cluster.conf is invalid ccs prints a more helpful error message and exits gracefully
Easy to replicate:
[root@ask-03 ~]# echo "<test>" > /tmp/blah
[root@ask-03 ~]# ccs -f /tmp/blah --getconf
Traceback (most recent call last):
File "/usr/sbin/ccs", line 2143, in <module>
main(sys.argv[1:])
File "/usr/sbin/ccs", line 240, in main
if (getconf): get_cluster_conf()
File "/usr/sbin/ccs", line 588, in get_cluster_conf
xml = get_cluster_conf_xml()
File "/usr/sbin/ccs", line 746, in get_cluster_conf_xml
dom = minidom.parseString(xml)
File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/minidom.py", line 1925, in parseString
return expatbuilder.parseString(string)
File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 942, in parseString
return builder.parseString(string)
File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: no element found: line 2, column 0
It should just print out an error saying something to the effect of "Bad cluster file specified."
Using ricci-0.16.2-48.el6:
[root@ask-04 tmp]# echo "<test>" > /tmp/blah
[root@ask-04 tmp]# ccs -f /tmp/blah --getconf
Cluster configuration file specified is not in a valid xml format.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: ccs is used to parse an invalid cluster.conf file
Consequence: ccs issues a traceback
Fix: ccs now checks to see if the cluster.conf is invalid
Result: If cluster.conf is invalid ccs prints a more helpful error message and exits gracefully
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0898.html
Easy to replicate: [root@ask-03 ~]# echo "<test>" > /tmp/blah [root@ask-03 ~]# ccs -f /tmp/blah --getconf Traceback (most recent call last): File "/usr/sbin/ccs", line 2143, in <module> main(sys.argv[1:]) File "/usr/sbin/ccs", line 240, in main if (getconf): get_cluster_conf() File "/usr/sbin/ccs", line 588, in get_cluster_conf xml = get_cluster_conf_xml() File "/usr/sbin/ccs", line 746, in get_cluster_conf_xml dom = minidom.parseString(xml) File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/minidom.py", line 1925, in parseString return expatbuilder.parseString(string) File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 942, in parseString return builder.parseString(string) File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) xml.parsers.expat.ExpatError: no element found: line 2, column 0 It should just print out an error saying something to the effect of "Bad cluster file specified."