RabbitMQ OCF script requires manual intervention in rare cases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Vladimir Kuklin | ||
5.1.x |
Confirmed
|
Medium
|
Vladimir Kuklin | ||
6.0.x |
Confirmed
|
Medium
|
Vladimir Kuklin | ||
6.1.x |
Confirmed
|
Medium
|
Fuel Library (Deprecated) |
Bug Description
{"build_id": "2014-11-
Steps to reproduce:
1. Deploy cluster with configuration (on Hardware lab):
Centos HA, Neutron VLAN, 5 Controllers, 7 Computes
2. Execute on Primary controller "shutdown -h now"
3. Wait ~20 min
Expected result:
Cluster will be in correct state
Actual result:
Cluster is in incorrect state.
See the attached log (rabbit@node-3).
After shutting down node-2
[root@node-3 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-3' ...
[{nodes,
...done.
Changed in fuel: | |
status: | Incomplete → Confirmed |
milestone: | 5.1.1 → 6.0 |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
status: | Confirmed → Incomplete |
summary: |
- Handshake_timeout of rabbit after destructive actions + Handshake_timeout of rabbit after connectivity issues |
summary: |
- Handshake_timeout of rabbit after connectivity issues + RabbitMQ OCF script requires manual intervention in rare cases |
Please explain impact of this bug in more details and change the summary to something more specific than just "incorrect work".