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:
In bz1176018 we added support for pacemaker authkey. The authkey is automatically created and distributed by pcs. However pcs always reads it from and writes it to /etc/pacemaker/authkey. If a custom location for the authkey is specified in /etc/sysconfig/pacemaker, pcs ignores it. This leads to missing authkey from pacemaker point of view.


Version-Release number of selected component (if applicable):
pcs-0.9.158-6.el7


How reproducible:
always, easily


Steps to Reproduce:
1. Change authkey path in /etc/sysconfig/pacemaker .
2. Setup a cluster, add remote or guest nodes.
3. Pacemaker authkey is stored at /etc/pacemaker/authkey instead of the location set in step 1, remote and guest nodes don't work.


Actual results:
Custom authkey location is ignored.


Expected results:
Custom authkey location is respected.


Additional info:
Backing up and restoring of cluster configuration needs to be fixed as well.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.