Bug 1641948
| Summary: | rabbitmq-cluster agent should fail monitor when node is in minority partition [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED ERRATA | QA Contact: | Marian Krcmarik <mkrcmari> |
| Severity: | urgent | Docs Contact: | Marek Suchánek <msuchane> |
| Priority: | urgent | ||
| Version: | 7.5 | CC: | agk, aherr, cfeist, chjones, cluster-maint, ctowsley, fdinitto, jeckersb, lmiccini, mjuricek, mkrcmari, morazi, oalbrigt, rzaleski, sbradley |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | resource-agents-3.9.5-124.el7_5.3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, monitor action succeeded on all nodes when the RabbitMQ message broker got into a partitioned state without triggering a fencing action. As a consequence, the cluster remained partitioned indefinitely. With this update, monitor action now fails when node is in minority partition. As a result, nodes in minority partition get fenced as expected.
|
Story Points: | --- |
| Clone Of: | 1639826 | Environment: | |
| Last Closed: | 2018-11-06 16:16:37 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: | 1639826 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-10-23 08:33:11 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, 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-2018:3513 |