Bug 1213941

Summary:	Cluster standby command hard codes hostname
Product:	Red Hat Enterprise Linux 7	Reporter:	glennduffy
Component:	pcs	Assignee:	Chris Feist <cfeist>
Status:	CLOSED DUPLICATE	QA Contact:	cluster-qe <cluster-qe>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	cluster-maint, glennduffy, tojeline
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-22 09:04:09 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:

Description glennduffy 2015-04-21 15:10:34 UTC

Description of problem:
When invoking 'pcs cluster standby', an error shows up indicating that the node does not appear in the configuration. The node name that is printed with the error is the hostname of the system, rather than the node name, which is different. Invoking pcs cluster standby [node_name] works just fine. 

Version-Release number of selected component (if applicable):
pcs version 0.9.137

How reproducible:
Always

Steps to Reproduce:
1. Configure a cluster where the node names are different than the host names.
2. Start the cluster
3. Invoke pcs cluster standby on one of the nodes.

Actual results:
[root@linux-ha-1 pcs]# pcs cluster standby
Error: node 'linux-ha-1' does not appear to exist in configuration

Expected results:
[root@linux-ha-1 pcs]# pcs cluster standby
[root@linux-ha-1 pcs]#

Additional info:
I can clearly see the bug in /usr/lib/python2.7/site-packages/pcs/cluster.py in function node_standby(). If the length of the input argument array is 0, the code populates the argument with the result of uname -n. This should be changed to retrieve the node name, not the host name.

Comment 2 Tomas Jelinek 2015-04-22 09:04:09 UTC


*** This bug has been marked as a duplicate of bug 1205653 ***