The fencing history of a pacemaker cluster shows the incorrect date and time

Solution Verified - Updated -

Issue

  • The fencing history of a pacemaker cluster shows the incorrect date and time.

     # pcs status --full | grep "Fencing History" -A 2
 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'

Environment

  • Red Hat Enterprise Linux Server 8, 9 (with the High Availability Add On)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content