Bug 2189301 - Rebase pacemaker on upstream 2.1.6 release
Summary: Rebase pacemaker on upstream 2.1.6 release
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: 9.2
Hardware: All
OS: All
high
high
Target Milestone: rc
: 9.3
Assignee: Chris Lumens
QA Contact: cluster-qe
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-24 17:19 UTC by Chris Lumens
Modified: 2023-08-17 13:38 UTC (History)
5 users (show)

Fixed In Version: pacemaker-2.1.6-4.el9
Doc Type: Enhancement
Doc Text:
.Rebase Pacemaker packages to version: 2.1.6 The Pacemaker packages have been upgraded to upstream version 2.1.6, which provides a number of enhancements and bug fixes over the previous version. The following features have been added: * Previously, when a Pacemaker Remote connection was lost, Pacemaker would always purge its transient node attributes. This was unnecessary if the connection was quickly recoverable and the remote daemon had not restarted in the meantime. Pacemaker Remote nodes now preserve transient node attributes after a brief, recoverable connection outage. * The `alert_snmp.sh.sample` alert agent, which is the sample alert agent provided with Pacemaker, now supports the SNMPv3 protocol as well as SNMPv2. With this update, You can copy the `alert_snmp.sh.sample` agent without modification to use SNMPv3 with Pacemaker alerts. * Pacemaker alerts and alert recipients now support an `enabled` meta option. Setting this option to `false` for an alert disables the alert. Setting this option to `true` for an alert and `false` for a particular recipient disables the alert for that recipient. The default value for this option is `true`. You can use this option to temporarily disable an alert for any reason, such as planned maintenance. The following bugs have been fixed: * Pacemaker Designated Controller elections no longer finalized until all pending actions are complete and no action results are lost. * The `fence_scsi` agent is now able to auto-detect shared `lvmlockd` devices when the 'devices' attribute is not set. * Resource stickiness now properly compares against colocation scores. * The `crm_resource` command now allows banning or moving a bundle with only a single active replica. * Previously, promotable clone instances were assigned in numerical order, with promoted instances first. As a result, if a promoted clone instance needed to start, an unpromoted instance in some cases restarted unexpectedly, because the instance numbers changed. With this fix, roles are considered when assigning instance numbers to nodes and as a result no unnecessary restarts occur.
Clone Of:
Environment:
Last Closed:
Type: Component Upgrade
Target Upstream Version: 2.1.6
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6701 0 None None None 2023-05-16 14:17:15 UTC
Red Hat Issue Tracker RHELPLAN-155575 0 None None None 2023-04-24 17:20:29 UTC
Red Hat Knowledge Base (Solution) 3615211 0 None None None 2023-08-16 20:17:42 UTC
Red Hat Knowledge Base (Solution) 4849731 0 None None None 2023-08-16 20:07:50 UTC
Red Hat Knowledge Base (Solution) 5374451 0 None None None 2023-08-16 20:16:55 UTC
Red Hat Knowledge Base (Solution) 6955674 0 None None None 2023-08-16 20:13:22 UTC
Red Hat Knowledge Base (Solution) 6971897 0 None None None 2023-08-16 20:02:53 UTC
Red Hat Knowledge Base (Solution) 6972370 0 None None None 2023-08-16 20:04:03 UTC
Red Hat Knowledge Base (Solution) 6993764 0 None None None 2023-08-16 19:59:47 UTC

Description Chris Lumens 2023-04-24 17:19:50 UTC
ClusterLabs is expected to release Pacemaker 2.1.6 in time for RHEL 9.3, with fixes for multiple RHEL BZs, so we would like to rebase on that.

Comment 1 Chris Lumens 2023-04-24 17:56:26 UTC
At the moment, we only have 8.9 bugs filed for most of the things that will be fixed by this rebase so I'm linking to those here.

Bugs to be addressed by this rebase:

bz2160206
bz2010084
bz2182482
bz2106642
bz1578820
bz2030869
bz1632951
bz1876173
bz2078611
bz2106642
bz1931023
bz2095443


Note You need to log in before you can comment on or make changes to this bug.