Bug 1470105 - Support custom location of pacemaker authkey
Support custom location of pacemaker authkey
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Tomas Jelinek
Steven J. Levine
Depends On:
Blocks: 1470215
  Show dependency treegraph
Reported: 2017-07-12 08:04 EDT by Tomas Jelinek
Modified: 2017-11-13 05:39 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1470215 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Jelinek 2017-07-12 08:04:52 EDT
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):

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.

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