I was trying to reproduce this bug using 2nd variant (3 controllers + 3 monogs + compute with ceilo + cinder). And I succeed with it.
It does seem like right after shutting down one of the nodes it takes time for rabbit to rebalance its cluster. But if I'd run again set of smoke tests it would be completed with all "thumbs up" due to availability of rabbit cluster (of two nodes), so it wouldn't fail due to the same problem as for the first run.
I would try to figure out the most appropriate workarounds for cases when rabbitmq trying to rebalance.
Hello to All.
I was trying to reproduce this bug using 2nd variant (3 controllers + 3 monogs + compute with ceilo + cinder). And I succeed with it.
It does seem like right after shutting down one of the nodes it takes time for rabbit to rebalance its cluster. But if I'd run again set of smoke tests it would be completed with all "thumbs up" due to availability of rabbit cluster (of two nodes), so it wouldn't fail due to the same problem as for the first run.
I would try to figure out the most appropriate workarounds for cases when rabbitmq trying to rebalance.
Here what cinder-volume shows https:/ /gist.github. com/denismakogo n/4d7832f95f6fd 8c70236 (pretty similar thing was shown by nova-compute).