Bug 2189301
Summary: | Rebase pacemaker on upstream 2.1.6 release | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Chris Lumens <clumens> |
Component: | pacemaker | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | high | Docs Contact: | Steven J. Levine <slevine> |
Priority: | high | ||
Version: | 9.2 | CC: | cluster-maint, gfialova, jrehova, kgaillot, sbradley, slevine |
Target Milestone: | rc | Keywords: | Rebase, Triaged |
Target Release: | 9.3 | Flags: | pm-rhel:
mirror+
|
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
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 several 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 and 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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-07 08:23:06 UTC | Type: | Component Upgrade |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | 2.1.6 |
Embargoed: |
Description
Chris Lumens
2023-04-24 17:19:50 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 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/RHEA-2023:6314 |