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.
Bug 1283627 - reading nodes id from pacemaker does not work on RHEL6
Summary: reading nodes id from pacemaker does not work on RHEL6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-19 12:55 UTC by Tomas Jelinek
Modified: 2016-05-10 19:27 UTC (History)
4 users (show)

Fixed In Version: pcs-0.9.148-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: User creates a one-node cluster. Consequence: "pcs status" command crashes with traceback. Fix: Removed code which was dealing with pacemaker's node list trying to read pacemaker's node IDs as those are not supported nor needed on RHEL6 clusters. Result: "pcs status" command works properly.
Clone Of:
Environment:
Last Closed: 2016-05-10 19:27:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (3.16 KB, patch)
2015-11-25 14:53 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0739 0 normal SHIPPED_LIVE pcs bug fix update 2016-05-10 22:29:32 UTC

Description Tomas Jelinek 2015-11-19 12:55:16 UTC 
Reading nodes id from pacemaker does not work correctly on RHEL6. It is because of different output from "crm_node -l" on RHEL6 comparing to RHEL7:
> RHEL7
[root@rh71-node1:~]# pcs status nodes pacemaker-id
1 rh71-node1
2 rh71-node2
[root@rh71-node1:~]# crm_node -l
1 rh71-node1 member
2 rh71-node2 member
> RHEL6
[root@rh67-node1:~]# pcs status nodes pacemaker-id
rh67-node1 rh67-node2
[root@rh67-node1:~]# crm_node -l
rh67-node1 rh67-node2

This causes crashes of "pcs status" when run on a one-node cluster, and possible another issues as well.
Comment 2 Tomas Jelinek 2015-11-25 14:53:28 UTC 
Created attachment 1098864 [details]
proposed fix

Test:

[root@rh67-node3:~]# pcs cluster setup --name=onenode rh67-node3 --start
rh67-node3: Updated cluster.conf...
Starting cluster on nodes: rh67-node3...
rh67-node3: Starting Cluster...

Before fix:
[root@rh67-node3:~]# pcs status
Cluster name: onenode
WARNING: no stonith devices and stonith-enabled is not false
Traceback (most recent call last):
  File "/usr/sbin/pcs", line 155, in <module>
    main(sys.argv[1:])
  File "/usr/sbin/pcs", line 147, in main
    status.status_cmd(argv)
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 13, in status_cmd
    full_status()
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 53, in full_status
    if utils.corosyncPacemakerNodeCheck():
  File "/usr/lib/python2.6/site-packages/pcs/utils.py", line 1975, in corosyncPacemakerNodeCheck
    pm_nodes = getPacemakerNodesID()
  File "/usr/lib/python2.6/site-packages/pcs/utils.py", line 1970, in getPacemakerNodesID
    pm_nodes[node_info[0]] = node_info[1]
IndexError: list index out of range

After fix:
[root@rh67-node3:~]# pcs status
Cluster name: onenode
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Nov 25 15:48:29 2015
Last change: Wed Nov 25 15:48:24 2015
Stack: cman
Current DC: rh67-node3 - partition with quorum
Version: 1.1.11-97629de
1 Nodes configured
0 Resources configured


Online: [ rh67-node3 ]

Full list of resources:


PCSD Status:
  rh67-node3: Online
Comment 3 Tomas Jelinek 2015-12-09 16:28:46 UTC 
Before Fix:
[root@rh67-node3:~]# rpm -q pcs
pcs-0.9.139-9.el6.x86_64
[root@rh67-node3:~]# pcs cluster setup --name=onenode rh67-node3 --start
rh67-node3: Updated cluster.conf...
Starting cluster on nodes: rh67-node3...
rh67-node3: Starting Cluster...
[root@rh67-node3:~]# pcs status
Cluster name: onenode
WARNING: no stonith devices and stonith-enabled is not false
Traceback (most recent call last):
  File "/usr/sbin/pcs", line 155, in <module>
    main(sys.argv[1:])
  File "/usr/sbin/pcs", line 147, in main
    status.status_cmd(argv)
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 13, in status_cmd
    full_status()
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 53, in full_status
    if utils.corosyncPacemakerNodeCheck():
  File "/usr/lib/python2.6/site-packages/pcs/utils.py", line 1975, in corosyncPacemakerNodeCheck
    pm_nodes = getPacemakerNodesID()
  File "/usr/lib/python2.6/site-packages/pcs/utils.py", line 1970, in getPacemakerNodesID
    pm_nodes[node_info[0]] = node_info[1]
IndexError: list index out of range



After Fix:
[root@rh67-node3:~]# rpm -q pcs
pcs-0.9.148-1.el6.x86_64
[root@rh67-node3:~]# pcs cluster setup --name=onenode rh67-node3 --start
Destroying cluster on nodes: rh67-node3...
rh67-node3: Stopping Cluster (pacemaker)...
rh67-node3: Successfully destroyed cluster

Sending cluster config files to the nodes...
rh67-node3: Updated cluster.conf...

Starting cluster on nodes: rh67-node3...
rh67-node3: Starting Cluster...

Synchronizing pcsd certificates on nodes rh67-node3...
rh67-node3: Success

Restarting pcsd on the nodes in order to reload the certificates...
rh67-node3: Success
[root@rh67-node3:~]# pcs status
Cluster name: onenode
WARNING: no stonith devices and stonith-enabled is not false
Last updated: Wed Dec  9 17:16:07 2015
Last change: Wed Dec  9 17:15:57 2015
Current DC: NONE
1 Nodes configured
0 Resources configured


Node rh67-node3: UNCLEAN (offline)

Full list of resources:


PCSD Status:
  rh67-node3: Online
Comment 7 errata-xmlrpc 2016-05-10 19:27:11 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2016-0739.html
Note You need to log in before you can comment on or make changes to this bug.