You don't even need to shut down a node to reproduce this problem, all you have to do is move the management vip to a different node with the following command (replace node-1 with hostname of the controller node that doesn't currently have the vip):
After that, most OpenStack services become unable to either put messages on RabbitMQ queues, take messages off the queues, or acknowledge the messages.
You don't even need to shut down a node to reproduce this problem, all you have to do is move the management vip to a different node with the following command (replace node-1 with hostname of the controller node that doesn't currently have the vip):
crm_resource -r vip__management_old --move --node node-1
After that, most OpenStack services become unable to either put messages on RabbitMQ queues, take messages off the queues, or acknowledge the messages.