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 1555938 - Synchronize fence history on restarted nodes
Summary: Synchronize fence history on restarted nodes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.7
Assignee: Klaus Wenninger
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1461964 1608369
TreeView+ depends on / blocked
 
Reported: 2018-03-14 22:16 UTC by Ken Gaillot
Modified: 2019-08-06 12:54 UTC (History)
5 users (show)

Fixed In Version: pacemaker-1.1.20-1.el7
Doc Type: No Doc Update
Doc Text:
Mostly under-the-hood for end users
Clone Of:
Environment:
Last Closed: 2019-08-06 12:53:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2129 0 None None None 2019-08-06 12:54:08 UTC

Description Ken Gaillot 2018-03-14 22:16:30 UTC 
Description of problem: Pacemaker's stonithd synchronizes fence history across all nodes, but only since the local stonithd was started. If a node restarts, it loses any fence history from before it was started, leading to different history views (stonith_admin --history) from different nodes.

When a stonithd joins the cluster, any existing history should be synchronized to it. This would keep the view the same regardless of node, and preserve fence history across the active lifetime of the cluster.
Comment 1 Ken Gaillot 2018-06-26 22:03:58 UTC 
Moving to RHEL 7 to target 7.7. If this doesn't make RHEL 8 via initial rebase, it will be cloned for RHEL 8.
Comment 3 Klaus Wenninger 2018-08-17 13:43:20 UTC 
Available on 1.1-branch with
https://github.com/ClusterLabs/pacemaker/commit/a9ecba18a3cb3d0ab9157f87e27f9d25ac2a34a4
Comment 4 Ken Gaillot 2019-02-02 00:40:36 UTC 
QA: Start a cluster with multiple nodes. Fence one of them. When the fenced node reboots and rejoins the cluster, run "stonith_admin --history '*'" on it. Before the fix, it will show nothing; after the fix, it will show the actual fence history.
Comment 5 Patrik Hagara 2019-03-20 10:24:30 UTC 
qa-ack+

reproducer in comment#4
Comment 7 Michal Mazourek 2019-06-12 14:25:44 UTC 
BEFORE (pacemaker-1.1.19-8.el7)
======
## Fence one node
[root@virt-186 ~]# pcs stonith fence virt-178
Node: virt-178 fenced

## Wait for the fenced node to join cluster again and check its stonith history
[root@virt-178 ~]# stonith_admin --history '*'
[root@virt-178 ~]#

## Other nodes of the cluster
[root@virt-186 ~]# stonith_admin --history '*'
virt-187 was able to reboot node virt-178 on behalf of stonith_admin.16457 from virt-186 at Wed Jun 12 15:17:37 2019

AFTER (pacemaker-1.1.20-5.el7)
=====
## Fence one node
[root@virt-022 ~]# pcs stonith fence virt-018
Node: virt-018 fenced

## Wait for the fenced node to join cluster again and check its stonith history
[root@virt-018 ~]# stonith_admin --history '*'
virt-012 was able to reboot node virt-018 on behalf of stonith_admin.11812 from virt-022 at Wed Jun 12 15:56:56 2019

## Now its synchronized with the stonith history on other nodes
[root@virt-022 ~]# stonith_admin --history '*'
virt-012 was able to reboot node virt-018 on behalf of stonith_admin.11812 from virt-022 at Wed Jun 12 15:56:56 2019

RESULT
======
Before the fix, fenced node lost any stonith history from before. Now the stonith history is synchronized with other nodes, even after reboot.

Verified for version pacemaker-1.1.20-5.el7
Comment 9 errata-xmlrpc 2019-08-06 12:53:38 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:2129
Note You need to log in before you can comment on or make changes to this bug.