Deployment fails during controllers removal: execution of '/usr/sbin/rabbitmq-plugins list -E -m' command expired
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
In Progress
|
High
|
Kyrylo Galanov | ||
8.0.x |
Confirmed
|
High
|
Fuel Library (Deprecated) |
Bug Description
Deployment fails during controllers removal, because puppet task 'rabbitmq.pp' returns error on primary controller after 2 other controllers are removed:
2015-12-29 02:51:56 +0000 /Stage[
2015-12-29 02:51:56 +0000 Puppet (debug): Executing '/usr/sbin/
2015-12-29 02:52:06 +0000 /Stage[
All commands which try to connect to RabbitMQ hang on primary controller, for example:
root@node-1:~# time /usr/sbin/
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
(v)ersion (k)ill (D)b-tables (d)istribution
real 12m52.051s
user 0m0.653s
sys 0m0.180s
Also RabbitMQ daemon is dead on all controllers:
Master/Slave Set: master_
Stopped: [ node-2.
Steps to reproduce:
1. Create cluster
2. Add 1 controller node
3. Deploy the cluster
4. Check swift, and invoke swift-rings-
on primary controller if check failed
5. Add 2 controller nodes
6. Deploy changes
7. Check swift, and invoke swift-rings-
on primary controller if check failed
8. Run OSTF
9. Add 2 controller 1 compute nodes
10. Deploy changes
11. Check swift, and invoke swift-rings-
on all the controllers
12. Run OSTF
13. Delete 2 controllers.
14. Deploy changes
Expected result: nodes are successfully removed, cluster is operational
Actual result: node are removed, but re-deployment of alive controller failed, cluster has 'error' status
Diagnostic snapshot: https:/
Changed in fuel: | |
milestone: | none → 9.0 |
tags: | added: area-library |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: team-bugfix |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Kyrylo Galanov (kgalanov) |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: life-cycle-management |
In step 13 primary controller is deleted. That may cause rabbitmq failure.