Bug 2128035
| Summary: | Pacemaker does not abort transition if resource configuration is moved [rhel-9.1.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | pacemaker | Assignee: | Reid Wahl <nwahl> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 9.1 | CC: | cfeist, cluster-maint, cluster-qe, kgaillot, mjuricek, nwahl, toneata |
| Target Milestone: | rc | Keywords: | Regression, Triaged, ZStream |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.4-5.el9_1.1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Pacemaker no longer rechecks resource assignments when the order of resources in the CIB changes, with no changes to the resource definitions.
Consequence: If the configuration reordering would cause resources to move, that will not be done until the next natural transition (up to the value of the cluster-recheck-interval property). This will generally not be a problem if stickiness is used.
Fix: Pacemaker again rechecks resource assignments when the order of resources in the CIB changes.
Result: The cluster responds immediately if needed.
|
Story Points: | --- |
| Clone Of: | 2125337 | Environment: | |
| Last Closed: | 2022-11-15 15:58:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2125337 | ||
| Bug Blocks: | |||
|
Comment 1
Chris Lumens
2022-10-20 14:19:38 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 (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:8428 |