Bug 2072108
| Summary: | Rebase pacemaker on upstream 2.1.4 release [9.1] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Ken Gaillot <kgaillot> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | high | Docs Contact: | Steven J. Levine <slevine> |
| Priority: | high | ||
| Version: | 9.1 | CC: | cluster-maint, msmazova, sbradley, slevine |
| Target Milestone: | rc | Keywords: | Rebase, Triaged |
| Target Release: | 9.1 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.4-2.el9 | Doc Type: | Enhancement |
| Doc Text: |
.Pacemaker rebased to version 2.1.4
The Pacemaker packages have been upgraded to the upstream version of Pacemaker 2.1.4. Notable changes include:
* The `multiple-active` resource parameter now accepts a value of `stop_unexpected`, The `multiple-active` resource parameter determines recovery behavior when a resource is active on more than one node when it should not be. By default, this situation requires a full restart of the resource, even if the resource is running successfully where it should be. A value of `stop_unexpected` for this parameter specifies that only unexpected instances of a multiply-active resource are stopped. It is the user's responsibility to verify that the service and its resource agent can function with extra active instances without requiring a full restart.
* Pacemaker now supports the `allow-unhealthy-node` resource meta-attribute. When this meta-attribute is set to `true`, the resource is not forced off a node due to degraded node health. When health resources have this attribute set, the cluster can automatically detect if the node's health recovers and move resources back to it.
* Users can now specify Access Control Lists (ACLS) for a system group using the `pcs acl group` command. Pacemaker previously allowed ACLs to be specified for individual users, but it is sometimes simpler and would conform better with local policies to specify ACLs for a system group, and to have them apply to all users in that group. This command was present in earlier releases but had no effect.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 09:49:38 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.3 |
| Embargoed: | |||
|
Description
Ken Gaillot
2022-04-05 15:53:50 UTC
QA: This rebase includes the RHEL 9 equivalents of the following RHEL 8 bzs: - Bug 1930578 - Bug 2036815 - Bug 2059638 - Bug 2065812 - Bug 2086230 QA: The latest build includes the equivalent of these RHEL 8 bzs in addition to the ones in Comment 2: * rhbz2055935 * rhbz2094855 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-2022:7937 |