Bug 1265425

Summary: pcs is not parsing the output of crm_node properly
Product: Red Hat Enterprise Linux 7 Reporter: Chris Feist <cfeist>
Component: pcsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: cluster-maint, fdinitto, rsteiger, tlavigne, tojeline
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.143-11.el7 Doc Type: Bug Fix
Doc Text:
No docs needed for this bz.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:38:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix for bug none

Description Chris Feist 2015-09-22 22:06:49 UTC 
crm_node output has changed in the latest pacemaker build

[root@virt-144 ~]# crm_node -l
4 virt-145
1 virt-142
3 virt-144

The new build however shows this (including an offline node):

[root@virt-145 ~]# crm_node -l
3 virt-144 member
2 virt-143 lost
1 virt-142 member
4 virt-145 member

We just need to update pcs to split on " " without a limit of 1 split.

Then if there's a 3rd field and it's 'lost', we just ignore that line, otherwise we continue.
Comment 1 Chris Feist 2015-09-22 22:16:01 UTC 
To test:

With new pacemaker, two hosts host-600, host-604 (600 is down).

Old pcs:
[root@host-604 pcs]# pcs status nodes pacemaker-id
1 host-600 lost
2 host-604 member

New pcs (with fix):
[root@host-604 pcs]# ./pcs status nodes pacemaker-id
2 host-604
Comment 2 Chris Feist 2015-09-22 22:16:38 UTC 
Created attachment 1076049 [details]
Fix for bug
Comment 5 Chris Feist 2015-09-23 22:00:49 UTC 
Before Fix:

[root@host-604 ~]# rpm -q pcs
pcs-0.9.143-9.el7.x86_64
[root@host-604 ~]# pcs status nodes pacemaker-id
1 host-600 lost
2 host-604 member
[root@host-604 ~]# pcs status | grep "WARNING: coro"
WARNING: corosync and pacemaker node names do not match (IPs used in setup?)


After Fix:
[root@host-604 ~]# rpm -q pcs
pcs-0.9.143-11.el7.x86_64
[root@host-604 ~]# pcs status nodes pacemaker-id
2 host-604
[root@host-604 ~]# pcs status | grep "WARNING: coro"
[root@host-604 ~]#
Comment 9 errata-xmlrpc 2015-11-19 09:38:49 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/RHSA-2015-2290.html