RabbitMQ-server doesn't start after safe reboot primary controller
Bug #1289210 reported by
Andrey Sledzinskiy
This bug report is a duplicate of:
Bug #1288831: RabbitMQ cluster locks up when a member is removed.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
New
|
Medium
|
Fuel Library (Deprecated) | ||
Bug Description
Bug is reproduced on ISO#235
Steps:
1. Create next env - Centos, Multi-node with HA, Neutron with GRE segmentation
2. Add 3 controllers, 1 compute, 1 cinder lvm
3. Deploy environment
4. Make safe reboot on primary controller with 'shutdown -r now'
Actual result - RabbitMQ-server doesn't start on primary controller
Fuel snapshot is attached.
Revision history for this message
| Andrey Sledzinskiy (asledzinskiy) wrote | #1 |
| Changed in fuel: | |
| assignee: | nobody → Fuel Library Team (fuel-library) |
| milestone: | none → 4.1.1 |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #2 |
To post a comment you must log in.
As I can see from the logs, multiple RabbitMQ log mesasages "Discarding message {'$gen_call" point this issue has many common with https:/