View Issue Details

IDProjectCategoryView StatusLast Update
0014210CentOS-7pcspublic2018-01-10 15:13
Status newResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0014210: pcs cluster standby fails
DescriptionI am not sure if this is a bug or behavior change.
But I need a way to run this command successfully.

Previously was using CentOS 7.3.1611.
Recently upgraded to 7.4
# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

The HA cluster with 2 nodes is set up.
But I see below error while
# pcs cluster standby
Error: unable to get local node name from pacemaker: node name is null
# rpm -qa | grep pcs

The same command used to run successfully on previous CentOS release.
To confirm this I downgraded the pcs to an older version and tested.
# rpm -qa | grep pcs
# pcs cluster standby

I have run this command in debug and attached the console outputs.
Seems these 2 versions of pcs run a different crm command internally.
Steps To Reproduce- Install a CentOS 7.4.1708.
- Setup a HA cluster (pacemaker + corosync) with 2 nodes and one clone resource using pcs commands.
- Run command "pcs cluster standby" on any node in the cluster.
TagsNo tags attached.




2017-11-30 03:35


pcs_standby.logs (13,361 bytes)


2018-01-10 15:13

reporter   ~0030905

I also had this problem. Somehow the internal way to determine the nodename has changed. You can use the following methods to fix the issue:

1. Use the local nodename in the command. I.e.: pcs cluster standby mynode
2. Enter the nodename in the /etc/corosync/corosync.conf file under the node definitions in the nodelist. You can add 'name: mynode' under each node definition. Do this on all nodes in the cluster!

I have no idea what changed, but something did ...

Issue History

Date Modified Username Field Change
2017-11-30 03:35 abhayyb New Issue
2017-11-30 03:35 abhayyb File Added: pcs_standby.logs
2017-11-30 03:35 abhayyb Tag Attached: console
2017-11-30 03:39 abhayyb Tag Detached: console
2018-01-10 15:13 shoenix Note Added: 0030905