Bug 1425317
Summary: | pcs auth will fail with false error message if pcsd-cli.rb outputs to stderr | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xu Yin <xyin> |
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.3 | CC: | cfeist, cluster-maint, idevat, mlisik, mmazoure, nwahl, omular, rsteiger, sbradley, tojeline |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pcs-0.9.156-1.el7 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
The user runs the "pcs cluster auth" command.
Consequence:
Sometimes the command may exit with an error even though it actually succeeded.
Fix:
Properly parse the output of a script which does the actual authentication.
Result:
The "pcs cluster auth" command works.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 18:26:07 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
Xu Yin
2017-02-21 07:57:06 UTC
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 |