Bug 1666148 - [RFE] Add an option to configure fence_kdump for pacemaker cluster running on controller nodes.
Summary: [RFE] Add an option to configure fence_kdump for pacemaker cluster running on...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 13.0 (Queens)
Hardware: All
OS: Linux
medium
medium
Target Milestone: z9
: 13.0 (Queens)
Assignee: Luca Miccini
QA Contact: pkomarov
URL:
Whiteboard:
Depends On: 1699450 1699451
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-15 03:10 UTC by Keigo Noha
Modified: 2023-03-24 14:37 UTC (History)
11 users (show)

Fixed In Version: puppet-tripleo-8.5.1-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 14:01:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 682236 0 None MERGED Implement stonith levels and enable kdump agent. 2020-12-01 03:49:57 UTC
Red Hat Issue Tracker OSP-23652 0 None None None 2023-03-24 14:37:07 UTC
Red Hat Product Errata RHBA-2019:3794 0 None None None 2019-11-07 14:01:36 UTC

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


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