Bug 1666148

Summary: [RFE] Add an option to configure fence_kdump for pacemaker cluster running on controller nodes.
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: puppet-tripleoAssignee: Luca Miccini <lmiccini>
Status: CLOSED ERRATA QA Contact: pkomarov
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aherr, dabarzil, ealcaniz, jjoyce, jschluet, lmiccini, mburns, mfuruta, ramishra, slinaber, tvignaud
Target Milestone: z9Keywords: FutureFeature, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-tripleo-8.5.1-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 14:01:17 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: 1699450, 1699451    
Bug Blocks:    

Description Keigo Noha 2019-01-15 03:10:17 UTC 
Description of problem:
Add an option to configure fence_kdump for pacemaker cluster running on controller nodes.

Currently, stonith device is configured with ipmi or another power management tools, e.g. idrac, ilo.

In RHEL side, kdump should be enabled by our recommendation and ease to support in the case of kernel panic.
To capture the vmcore surely, we should add the parameter to add fence_kdump as primary stonith device to pacemaker cluster running on controller nodes.
Comment 5 errata-xmlrpc 2019-11-07 14:01:17 UTC 
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://access.redhat.com/errata/RHBA-2019:3794