Bug 1311180
| Summary: | rabbitmq-cluster agent needs to forget stopped cluster nodes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | resource-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | agk, cfeist, cluster-maint, djansa, dmaley, fdinitto, felipe.alfaro, jeckersb, jraju, jruemker, oalbrigt, ochalups, plemenko, royoung, snagar, ushkalim |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | resource-agents-3.9.5-54.el7_2.7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: rabbitmq doesnt forget members quick enough
Consequence: After fencing, a rabbitmq-cluster resource instance may not be able to rejoin the rabbitmq cluster.
Fix: Use "rabbitmqctl forget_cluster_node <node>" when a node is fenced
Result: Node is removed from cluster and can join again
|
Story Points: | --- |
| Clone Of: | 1247303 | Environment: | |
| Last Closed: | 2016-03-31 22:08:41 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: | 1247303 | ||
| Bug Blocks: | 1350073, 1357991, 1387985 | ||
|
Description
Jan Kurik
2016-02-23 14:48:54 UTC
verified resource-agents-3.9.5-54.el7
[root@overcloud-controller-0 heat-admin]# pcs resource show rabbitmq
Resource: rabbitmq (class=ocf provider=heartbeat type=rabbitmq-cluster)
Attributes: set_policy="ha-all ^(?!amq\.).* {"ha-mode":"all"}"
Meta Attrs: notify=true
Operations: start interval=0s timeout=100 (rabbitmq-start-interval-0s)
stop interval=0s timeout=90 (rabbitmq-stop-interval-0s)
monitor interval=10 timeout=40 (rabbitmq-monitor-interval-10)
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://rhn.redhat.com/errata/RHBA-2016-0556.html If someone still sees this issue, then please test this package: resource-agents-3.9.5-76.el7 |