Bug 1311005
| Summary: | rabbitmq-cluster resource instance may not be able to rejoin the rabbitmq cluster. | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Michele Baldessari <michele> | |
| Component: | openstack-tripleo-heat-templates | Assignee: | Jiri Stransky <jstransk> | |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 8.0 (Liberty) | CC: | achernet, mburns, rhel-osp-director-maint | |
| Target Milestone: | --- | |||
| Target Release: | 8.0 (Liberty) | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.10-1.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
The notify=true parameter was previously missing from the RabbitMQ Pacemaker resource. Consequently, RabbitMQ instances were unable to rejoin the RabbitMQ cluster. This update adds support for notify=true to the pacemaker resource agent for RabbitMQ, and adds notify=true to OpenStack director. As a result, RabbitMQ instances are now able to rejoin the RabbitMQ cluster.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1311025 (view as bug list) | Environment: | ||
| Last Closed: | 2016-04-07 21:48:01 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1311025 | |||
|
Description
Michele Baldessari
2016-02-23 07:41:59 UTC
openstack-tripleo-heat-templates-0.8.10-2.el7ost
[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)
[root@overcloud-controller-0 heat-admin]#
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/RHEA-2016-0604.html |