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 1595444 - RFE: ability to clear stonith history
Summary: RFE: ability to clear stonith history
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.7
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
: 1748376 (view as bug list)
Depends On: 1595422
Blocks: 1461964 1608369
TreeView+ depends on / blocked
 
Reported: 2018-06-26 22:12 UTC by Ken Gaillot
Modified: 2023-10-06 17:49 UTC (History)
17 users (show)

Fixed In Version: pcs-0.9.168-1.el7
Doc Type: Enhancement
Doc Text:
.The `pcs` commands now support display, cleanup, and synchronization of fencing history Pacemaker's fence daemon tracks a history of all fence actions taken (pending, successful, and failed). With this release, the `pcs` commands allow users to access the fencing history in the following ways: * The `pcs status` command shows failed and pending fencing actions * The `pcs status --full` command shows the entire fencing history * The `pcs stonith history` command provides options to display and clean up fencing history * Although fencing history is synchronized automatically, the `pcs stonith history` command now supports an `update` option that allows a user to manually synchronize fencing history should that be necessary
Clone Of: 1595422
: 1620190 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:09:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix + tests (27.86 KB, patch)
2019-07-16 15:51 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4378481 0 None None None 2019-08-30 07:46:56 UTC
Red Hat Product Errata RHBA-2020:0996 0 None None None 2020-03-31 19:10:00 UTC

Description Ken Gaillot 2018-06-26 22:12:09 UTC 
+++ This bug was initially created as a clone of Bug #1595422 +++

Description of problem: Pacemaker's fence daemon tracks a history of all fence actions (pending, successful, and failed) taken, which can be displayed by the stonith_admin --history command, and soon by crm_mon (pcs status). However there is no way to clear the history, which will be especially relevant if showing fence failures becomes the default in crm_mon as expected.

A possible interface is a new stonith_admin option, e.g. --clear-history. It may be worthwhile to accept an optional argument "failures" or "all" (defaulting to "all"), or perhaps "all" should be the only behavior.

+++

We will need corresponding functionality in pcs.
Comment 4 Tomas Jelinek 2019-07-16 15:50:01 UTC 
Pacemaker CLI interface:
* cleanup the history for a specified node / all nodes:
  stonith_admin --history <node>|* --cleanup
* display the history for a specified node / all nodes:
  stonith_admin --history <node>|* --verbose
* update the history for a specified node / all nodes:
  stonith_admin --history <node>|* --broadcast

To find out if fence history is supported check crm_mon.rng for presence of fence_history element.
Comment 5 Tomas Jelinek 2019-07-16 15:51:09 UTC 
Created attachment 1591105 [details]
proposed fix + tests

Backport from RHEL-8.0

New pcs commands introduced:
1) pcs stonith history show
Displays the whole fencing history, optionally filtered by one node name.
2) pcs stonith history cleanup
Cleans fencing history up, optionally filtered by one node name.
3) pcs stonith history update
Sync fencing history in the local cluster.

If a cluster is running pacemaker without fencing history support, the pcs commands exit with an error pointing that out.
Comment 8 Ivan Devat 2019-08-05 11:12:48 UTC 
After Fix:

[kid76 ~] $ rpm -q pcs
pcs-0.9.168-1.el7.x86_64

[kid76 ~] $ rpm -q pacemaker
pacemaker-1.1.19-8.el7.x86_64
[kid76 ~] $ pcs stonith history show
Error: Fence history is not supported, please upgrade pacemaker

[kid76 ~] $ rpm -q pacemaker
pacemaker-1.1.20-5.el7.x86_64

[kid76 ~] $ pcs stonith history show

> enforce stonith history record e.g. by turning of the node
[kid76 ~] $ pcs stonith history show
crmd.4619 at kid76 wishes to reboot node lion76 - 1 0
kid76 failed to reboot node lion76 on behalf of crmd.4619 from kid76 at Fri Aug  2 14:28:37 2019

kid76 failed to reboot node lion76 on behalf of crmd.4619 from kid76 at Fri Aug  2 14:29:38 2019
[kid76 ~] $ pcs stonith history cleanup
cleaning up fencing-history for node *
[kid76 ~] $ pcs stonith history show
crmd.4619 at kid76 wishes to reboot node lion76 - 1 0

[kid76 ~] $ pcs stonith history update
gather fencing-history from all nodes
[kid76 ~] $ echo $?
0
Comment 10 Tomas Jelinek 2019-09-03 13:24:00 UTC 
*** Bug 1748376 has been marked as a duplicate of this bug. ***
Comment 30 errata-xmlrpc 2020-03-31 19:09:37 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-2020:0996
Note You need to log in before you can comment on or make changes to this bug.