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.
Bug 1470215 - Document Support for custom location of pacemaker authkey
Summary: Document Support for custom location of pacemaker authkey
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-High_Availability_Add-On_Reference
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1470105
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-12 14:15 UTC by Steven J. Levine
Modified: 2020-09-22 15:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1470105
Environment:
Last Closed: 2020-09-22 15:43:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steven J. Levine 2017-07-12 14:15:07 UTC
Cloning this as a doc bug so that we can track the documentation when the feature is implemented.

+++ This bug was initially created as a clone of Bug #1470105 +++

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.

Comment 2 Steven J. Levine 2017-10-02 20:52:11 UTC
The feature this documents was moved to 7.6 so I'm moving this BZ as well (and removing it from the docs RPL)

Comment 3 Steven J. Levine 2018-08-22 19:09:19 UTC
Moving to 7.7 as per feature BZ this is cloned from.

Comment 5 Steven J. Levine 2019-06-04 16:14:04 UTC
Moving this to 7.7 as per the development BZ it is cloned from.

Comment 6 Steven J. Levine 2019-08-09 20:12:50 UTC
Moving to 7.8, as per the development BZ it is cloned from.

Comment 7 Steven J. Levine 2020-09-22 15:43:45 UTC
I am closing this BZ and moving the tracking of this documentation to a JIRA, as per our current processs. That will keep this BZ out of the list of old BZs that need to be closed but retain the tracking.

The replacement JIRA is here:

https://issues.redhat.com/browse/RHELPLAN-54686


Note You need to log in before you can comment on or make changes to this bug.