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:
The pcs authentication command (pcs cluster auth ...) does not trigger authentication of nodes against each other. Only the node where authentication command was executed is authenticated against listed nodes on command line.
Version-Release number of selected component (if applicable):
pcs-0.9.152-4.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. Run pcs authentication command on a cluster node
virt-270 - cluster node
virt-269 - cluster node
[root@virt-270 ~]# pcs cluster auth virt-269 virt-270
Username: hacluster
Password:
virt-270: Authorized
virt-269: Authorized
2. Check pcd status on other cluster node
[root@virt-269 ~]# pcs status pcsd virt-269 virt-270
virt-269: Unable to authenticate
virt-270: Unable to authenticate
Actual results:
Only the node where pcs authentication command was executed is authenticated against listed nodes on the command line.
Expected results:
The node where the authentication command was executed is authenticated against listed nodes and listed nodes are authenticated against themselves
[root@virt-100 ~]# pcs cluster auth virt-{101..110}
Username: hacluster
Password:
virt-109: Authorized
virt-108: Authorized
virt-107: Authorized
virt-110: Authorized
virt-105: Authorized
virt-104: Authorized
virt-103: Authorized
virt-102: Authorized
virt-101: Authorized
virt-106: Authorized
[root@virt-100 ~]# pcs status pcsd virt-{101..110}
virt-101: Online
virt-102: Online
virt-103: Online
virt-104: Online
virt-105: Online
virt-106: Online
virt-107: Online
virt-108: Online
virt-109: Online
virt-110: Online
Also there should be the same result of 'pcs status pcsd virt-101..110}' on the nodes virt-{101..110}.
Comment 3Jan Pokorný [poki]
2016-07-22 18:53:12 UTC
This would also let adherents of clufter's "pcs commands" output down.
ISTR it used to work correctly. Fixing this defect should be prioritized.
Clarification of the reproducer:
When I wrote "cluster node(s)" I actually meant nodes set apart for cluster. There should not be any cluster configuration on the nodes at the time of executing pcs authentication command.
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://rhn.redhat.com/errata/RHSA-2016-2596.html
Description of problem: The pcs authentication command (pcs cluster auth ...) does not trigger authentication of nodes against each other. Only the node where authentication command was executed is authenticated against listed nodes on command line. Version-Release number of selected component (if applicable): pcs-0.9.152-4.el7.x86_64 How reproducible: always Steps to Reproduce: 1. Run pcs authentication command on a cluster node virt-270 - cluster node virt-269 - cluster node [root@virt-270 ~]# pcs cluster auth virt-269 virt-270 Username: hacluster Password: virt-270: Authorized virt-269: Authorized 2. Check pcd status on other cluster node [root@virt-269 ~]# pcs status pcsd virt-269 virt-270 virt-269: Unable to authenticate virt-270: Unable to authenticate Actual results: Only the node where pcs authentication command was executed is authenticated against listed nodes on the command line. Expected results: The node where the authentication command was executed is authenticated against listed nodes and listed nodes are authenticated against themselves [root@virt-100 ~]# pcs cluster auth virt-{101..110} Username: hacluster Password: virt-109: Authorized virt-108: Authorized virt-107: Authorized virt-110: Authorized virt-105: Authorized virt-104: Authorized virt-103: Authorized virt-102: Authorized virt-101: Authorized virt-106: Authorized [root@virt-100 ~]# pcs status pcsd virt-{101..110} virt-101: Online virt-102: Online virt-103: Online virt-104: Online virt-105: Online virt-106: Online virt-107: Online virt-108: Online virt-109: Online virt-110: Online Also there should be the same result of 'pcs status pcsd virt-101..110}' on the nodes virt-{101..110}.