Bug 2062848
| Summary: | Add new multiple-active option for "stop unexpected instances" [rhel-8.6.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 8.6 | CC: | cfeist, cluster-maint, kgaillot, lmiccini, matteo.panella, mjuricek, patrizio.bassi, rbruzzon, sbradley |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | 8.6 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.2-4.el8_6.2 | Doc Type: | Enhancement |
| Doc Text: |
Feature: Pacemaker's "multiple-active" resource meta-attribute now accepts the value "stop_unexpected", which will stop only those instances of a resource detected to be wrongly multiply active that are running where they shouldn't be, leaving the intended location running, without restarting it.
Reason: Some services are not disrupted by extra instances and can remain running when the extra instances are stopped.
Result: There is less downtime for a service that is detected to be wrongly multiple active.
|
Story Points: | --- |
| Clone Of: | 2036815 | Environment: | |
| Last Closed: | 2022-06-28 15:12:39 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: | 2036815 | ||
| Bug Blocks: | |||
|
Comment 1
Ken Gaillot
2022-04-08 17:03:02 UTC
Fix merged upstream as of commit 4a5dcc521, new build coming soon 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 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-2022:5324 |