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.

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.

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