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 2031765 - Fencing history shows incorrect date & time
Summary: Fencing history shows incorrect date & time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: 9.0
Hardware: x86_64
OS: Linux
urgent
medium
Target Milestone: rc
: 9.0
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 2032027
TreeView+ depends on / blocked
 
Reported: 2021-12-13 12:06 UTC by Markéta Smazová
Modified: 2023-08-03 20:11 UTC (History)
3 users (show)

Fixed In Version: pacemaker-2.1.2-2.el9
Doc Type: No Doc Update
Doc Text:
This issue was not in a released build
Clone Of:
: 2032027 (view as bug list)
Environment:
Last Closed: 2022-05-17 12:20:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KCSOPP-1859 0 None None None 2023-07-25 18:18:04 UTC
Red Hat Issue Tracker RHELPLAN-105519 0 None None None 2021-12-13 12:10:50 UTC
Red Hat Knowledge Base (Solution) 7027106 0 None None None 2023-08-03 20:11:46 UTC
Red Hat Product Errata RHBA-2022:2293 0 None None None 2022-05-17 12:20:51 UTC

Description Markéta Smazová 2021-12-13 12:06:40 UTC 
Description of problem:

Fencing history shows incorrect date & time of completed actions.

Example:
Fencing History:
  * reboot of virt-142 successful: delegate=virt-141, client=pacemaker-controld.54108, origin=virt-141, completed='1970-01-01 02:41:53
+01:00'

Version-Release number of selected component (if applicable):

pacemaker-2.1.2-1.el9

How reproducible:
Always

Steps to Reproduce:
1. Configure cluster with fence device.
2. Cause failure on one of the nodes, so the node is fenced.
3. Run 'pcs status --full' and check "Fencing History".

Actual results:

[root@virt-141 ~]# pcs status --full
Cluster name: STSRHTS31857
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-141 (1) (version 2.1.2-1.el9-ada5c3b36e2) - partition with quorum
  * Last updated: Mon Dec 13 13:03:28 2021
  * Last change:  Mon Dec 13 11:19:31 2021 by root via cibadmin on virt-141
  * 2 nodes configured
  * 2 resource instances configured

Node List:
  * Online: [ virt-141 (1) virt-142 (2) ]

Full List of Resources:
  * fence-virt-141	(stonith:fence_xvm):	 Started virt-141
  * fence-virt-142	(stonith:fence_xvm):	 Started virt-141

Migration Summary:

Fencing History:
  * reboot of virt-142 successful: delegate=virt-141, client=pacemaker-controld.54108, origin=virt-141, completed='1970-01-01 02:41:53 +01:00'
  * reboot of virt-142 successful: delegate=virt-141, client=stonith_admin.60043, origin=virt-141, completed='1970-01-01 01:13:08 +01:00'

Tickets:

PCSD Status:
  virt-141: Online
  virt-142: Online

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled


Expected results:

To have a correct date & time of completed fencing action.

Additional info:
Comment 1 Ken Gaillot 2021-12-13 21:37:55 UTC 
This was a regression introduced in the upstream 2.1.2 release by commit f52bc8e.
Comment 3 Ken Gaillot 2021-12-15 17:19:42 UTC 
Fixed upstream as of commit 0339e89f
Comment 8 Ilias Romanos 2022-02-07 17:03:03 UTC 
[root@virt-027 ~]# rpm -q pacemaker
pacemaker-2.1.2-4.el9.x86_64

[root@virt-027 ~]# pcs status
Cluster name: STSRHTS23380
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-026 (version 2.1.2-4.el9-ada5c3b36e2) - partition with quorum
  * Last updated: Mon Feb  7 18:00:19 2022
  * Last change:  Mon Feb  7 17:56:55 2022 by root via cibadmin on virt-026
  * 2 nodes configured
  * 2 resource instances configured

Node List:
  * Online: [ virt-026 virt-027 ]

Full List of Resources:
  * fence-virt-026	(stonith:fence_xvm):	 Started virt-026
  * fence-virt-027	(stonith:fence_xvm):	 Started virt-027

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

[root@virt-027 ~]# pcs stonith fence virt-026
Node: virt-026 fenced

[root@virt-027 ~]# pcs status --full
Cluster name: STSRHTS23380
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-027 (2) (version 2.1.2-4.el9-ada5c3b36e2) - partition with quorum
  * Last updated: Mon Feb  7 18:01:51 2022
  * Last change:  Mon Feb  7 17:56:55 2022 by root via cibadmin on virt-026
  * 2 nodes configured
  * 2 resource instances configured

Node List:
  * Online: [ virt-026 (1) virt-027 (2) ]

Full List of Resources:
  * fence-virt-026	(stonith:fence_xvm):	 Started virt-027
  * fence-virt-027	(stonith:fence_xvm):	 Started virt-027

Migration Summary:

Fencing History:
  * reboot of virt-026 successful: delegate=virt-027, client=stonith_admin.59951, origin=virt-027, completed='2022-02-07 18:00:43 +01:00'

Tickets:

PCSD Status:
  virt-026: Online
  virt-027: Online

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
Comment 10 errata-xmlrpc 2022-05-17 12:20:40 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 (new packages: pacemaker), 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-2022:2293
Note You need to log in before you can comment on or make changes to this bug.