Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2011974

Summary: Rebase pacemaker in RHEL 9.0 on upstream 2.1.2
Product: Red Hat Enterprise Linux 9 Reporter: Ken Gaillot <kgaillot>
Component: pacemakerAssignee: Ken Gaillot <kgaillot>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: high    
Version: 9.0CC: cluster-maint, msmazova
Target Milestone: rcKeywords: Rebase, Triaged
Target Release: 9.0Flags: pm-rhel: mirror+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: pacemaker-2.1.2-1.el9 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase package(s) to version: 2.1.2 Highlights, important fixes, or notable enhancements: See comments
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 12:20:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version: 2.1.2
Embargoed:

Description Ken Gaillot 2021-10-07 20:13:17 UTC
ClusterLabs is expected to release Pacemaker 2.1.2 in time for RHEL 9.0 GA, with fixes for multiple RHEL BZs, so we would like to rebase on that.

Comment 1 Ken Gaillot 2021-12-01 00:36:50 UTC
QA: This rebase build contains the 9.0 equivalents of the following 8.6 fixes:

* Bug 1082146 (per-host fence delays in pcmk_delay_base)
* Bug 1281463 (metadata enums for pacemaker daemon metadata)
* Bug 1346014 (ensure crm-resource --force-* works with LSB resources)
* Bug 1376538 (spaces in pcmk_host_map)
* Bug 1384420 (ACL group name restricted to unique xml id)
* Bug 2027006 (update corosync version dependency; not particularly relevant since only 9.0alpha had a corosync version that isn't compatible)

In addition, 9.0 has some display changes compared to 8.6, due to different build options. "crm_mon" and "pcs status" will now show action failures in a more readable format. For example, in 8.6 some failed actions might look like:

    Failed Resource Actions:
      * ClusterIP:0_monitor_30000 on fc16-builder 'not running' (7): call=11, status='complete', last-rc-change='Wed Feb 22 11:04:34 2012', queued=0ms, exec=20ms
      * petulant_stop_0 on rhel7-1 'unknown' (198): call=323, status='Timed Out', last-rc-change='Wed Nov 28 12:35:41 2018', queued=0ms, exec=95134ms
      * vm_idcc_devel_migrate_to_0 on ha-idg-1 'error' (1): call=427, status='complete', exitreason='idcc_devel: live migration to ha-idg-2-private failed: 1', last-rc-change='Thu Jun  6 04:00:43 2019', queued=4ms, exec=657ms
      * rsc1_monitor_10000 on sles11-1 'not installed' (5): call=26, status='Not installed', last-rc-change='Thu Aug  8 20:20:39 2013', queued=0ms, exec=0ms
    
The same failures in 9.0 will look like:
    
    Failed Resource Actions:
      * ClusterIP:0 30s-interval monitor on fc16-builder returned 'not running' at Wed Feb 22 11:04:34 2012 after 20ms
      * petulant stop on rhel7-1 could not be executed (Timed Out) at Wed Nov 28 12:35:41 2018 after 1m35.134s
      * vm_idcc_devel migrate_to on ha-idg-1 returned 'error' because 'idcc_devel: live migration to ha-idg-2-private failed: 1' at Thu Jun  6 04:00:43 2019 after 657ms
      * rsc1 10s-interval monitor on sles11-1 could not be executed (Not installed) at Thu Aug  8 20:20:39 2013

In 9.0, crm_mon will show the 8.6-style format if --show-detail is given.

In addition, crm_mon/pcs status/logs will show promotable clone roles as "Promoted" and "Unpromoted" in 9.0 (instead of "Master" and "Slave" as in RHEL 8), and OCF resource agents will be shown like "ocf:pacemaker:Dummy" (instead of "ocf::pacemaker:Dummy").

Comment 6 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