Hide Forgot
Description of problem: When a node has ricci installed and running, but not clustermon, many ccs functions cause a backtrace. Version-Release number of selected component (if applicable): ricci-0.16.2-35.el6.x86_64 ccs-0.16.2-35.el6.x86_64 How reproducible: All the time Steps to Reproduce: 1. Have a node with ricci installed, but not cman 2. Run 'ccs -h localhost --getconf' on the node. Actual results: Backtrace. Expected results: Warning about clustermon not installed, or at least ricci not ready.
To replicate: [root@amoco-01 ~]# rpm -e --nodeps modcluster [root@amoco-01 ~]# ccs -h localhost --getconf Traceback (most recent call last): File "/usr/sbin/ccs", line 2144, 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 744, in get_cluster_conf_xml xml = send_ricci_command("cluster", "get_cluster.conf") File "/usr/sbin/ccs", line 2061, in send_ricci_command xml = dom.getElementsByTagName('function_response')[0].toxml() IndexError: list index out of range With new package: [cfeist@gold ccs]$ ./ccs -i -h amoco-01 --getconf Error: Unable to retrieve information from ricci (is modcluster installed?) [root@amoco-01 ~]# yum install modcluster ... [cfeist@gold ccs]$ ./ccs -i -h amoco-01 --getconf <cluster config_version="14" name="test"> <fence_daemon/> <clusternodes> <clusternode name="amoco-01.lab.msp.redhat.com" nodeid="1"/> <clusternode name="amoco-02.lab.msp.redhat.com" nodeid="2"/> </clusternodes> <cman/> <fencedevices/> <rm> <failoverdomains/> <resources/> </rm> </cluster> Commit: https://github.com/feist/ccs/commit/18a82dc730bde984344f1390be0b4dd9c58fd24b
Using ricci-0.16.2-48.el6: [root@ask-04 tmp]# rpm -e --nodeps modcluster [root@ask-04 tmp]# ccs -h localhost --getconf Error: Unable to retrieve information from ricci (is modcluster installed?)
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: No documentation necessary.
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