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.

+++ This bug was initially created as a clone of Bug #2166388 +++

Description of problem: If resource history is cleaned on a node with past live migration history for a resource, in some cases the resource (active elsewhere) could be unnecessarily recovered.


Version-Release number of selected component (if applicable): pacemaker-2.1.5-5.el9


How reproducible: Reliably


Steps to Reproduce:
1. Create and start a cluster with at least three nodes.
2. Create a migrateable resource, for example "pcs resource create migrator ocf:pacemaker:Stateful meta allow-migrate=true"
3. Ban the migrateable resource from its current node. It should live-migrate to a new node.
4. Ban the migrateable resource its new node. It should live-migrate to a third node.
5. Run "pcs resource refresh" for the migrateable resource with node= the second node that it was active on.

Actual results: The resource is restarted on its current node.

Expected results: No resource activity occurs after refreshing the middle node.

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 (pacemaker bug fix and enhancement update), 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-2023:2150