Bug 1470105

Summary: Support custom location of pacemaker authkey
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED WONTFIX QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact: Steven J. Levine <slevine>
Priority: medium    
Version: 7.4CC: cfeist, cluster-maint, idevat, omular, slevine, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1470215 (view as bug list) Environment:
Last Closed: 2021-01-15 07:39:44 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:
Bug Depends On:    
Bug Blocks: 1470215    

Description Tomas Jelinek 2017-07-12 12:04:52 UTC 
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 7 RHEL Program Management 2021-01-15 07:39:44 UTC 
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.