Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
Please backport https://github.com/ClusterLabs/pcs/issues/124 (patch https://github.com/ClusterLabs/pcs/commit/03f17f86f68675b8d20da664e66617ce3e614de4?diff=split)

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


How reproducible:


Steps to Reproduce:
1. Add a directory (With world writable permisson, like 666) to PATH.
2. # pcs cluster auth pcmk1 pcmk2 --debug
3.

Actual results:

Error: Unable to communicate with pcsd


Expected results:

pcmk1: Already authorized
pcmk2: Already authorized


Additional info:
In our environment (RHEL7.3), patching https://github.com/ClusterLabs/pcs/commit/03f17f86f68675b8d20da664e66617ce3e614de4?diff=split can solve the issue.

Patch in upstream:
https://github.com/ClusterLabs/pcs/commit/03f17f86f68675b8d20da664e66617ce3e614de4

Reproducer:
[root@rh73-node1:~]# chmod 777 /usr
[root@rh73-node1:~]# pcs cluster auth rh73-node1 rh73-node2 rh73-node3 -u hacluster -p password

Before fix:
[root@rh73-node1:~]# rpm -q pcs
pcs-0.9.152-10.el7_3.1.x86_64
[root@rh73-node1:~]# pcs cluster auth rh73-node1 rh73-node2 rh73-node3 -u hacluster -p password
Error: Unable to communicate with pcsd

After Fix:
[root@rh73-node1:~]# rpm -q pcs
pcs-0.9.156-1.el7.x86_64
[root@rh73-node1:~]# pcs cluster auth rh73-node1 rh73-node2 rh73-node3 -u hacluster -p password
rh73-node1: Authorized
rh73-node3: Authorized
rh73-node2: Authorized

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://access.redhat.com/errata/RHBA-2017:1958