| Summary: | ccs --status traceback without cluster | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Brian Brock <bbrock> |
| Component: | ricci | Assignee: | Chris Feist <cfeist> |
| Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | cluster-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ricci-0.16.2-34.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-05 23:46:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Error returned from ricci is now printed (instead of a traceback). [root@ask-02 ~]# mv /etc/cluster/cluster.conf /tmp/ mv: overwrite `/tmp/cluster.conf'? y [root@ask-02 ~]# ccs -h localhost --status Error: unable to read file /etc/cluster/cluster.conf [root@ask-02 ~]# mv /tmp/cluster.conf /etc/cluster/ [root@ask-02 ~]# ccs -h localhost --status <cluster alias="mycluster" cluster_version="6" config_version="41" minQuorum="2" name="mycluster" quorate="true" votes="3"> <node clustered="true" name="ask-02" nodeid="1" online="true" uptime="5452830" votes="1"/> <node clustered="true" name="ask-03" nodeid="2" online="true" uptime="7694957" votes="1"/> <node clustered="true" name="ask-04" nodeid="3" online="true" uptime="7694909" votes="1"/> </cluster> Rolling into main CLI bz. *** This bug has been marked as a duplicate of bug 614647 *** |
--status doesn't give the expected, correct output ccs-0.16.2-33.el6 reliable with no known workarounds `ccs -h <clu member> --status` against a system with no cluster members Actual results: -(~:$)-> ccs -h north-14 --status north-14 password: Traceback (most recent call last): File "/usr/sbin/ccs", line 1932, in <module> main(sys.argv[1:]) File "/usr/sbin/ccs", line 227, in main if (status): get_cluster_status() File "/usr/sbin/ccs", line 540, in get_cluster_status xml = minidom.parseString(xml).getElementsByTagName('cluster')[0].toprettyxml(indent=' ',newl='') IndexError: list index out of range Expected results: Message about incorrect usage or cluster that doesn't exist, not a traceback.