Revision history [back]

click to hide/show revision 1
initial version

To answer this part of your question After the reboot, the controller node shows the compute-services down but the compute services are up and running on the compute nodes. When rabbitmq is restarted it clears all of the queues, if the controller crashed and did not properly siginal the old queues as being closed to the compute node, the compute serivce still believes that the old queues are active and continue to send to them. Restarting the serivces on the compute node will force them to check if their queue is available and if not they will create a new one.

To answer this part of your question question

After the reboot, the controller node shows the compute-services down but the compute services are up and running on the compute nodes.

When rabbitmq is restarted it clears all of the queues, if the controller crashed and did not properly siginal the old queues as being closed to the compute node, the compute serivce still believes that the old queues are active and continue to send to them. Restarting the serivces on the compute node will force them to check if their queue is available and if not they will create a new one.

To answer this part of your question

After the reboot, the controller node shows the compute-services down but the compute services are up and running on the compute nodes.

When rabbitmq is restarted it clears all of the queues, if the controller crashed and did not properly siginal signal the old queues as being closed to the compute node, the compute serivce service still believes that the old queues are active and continue to send to them. Restarting the serivces services on the compute node will force them to check if their queue is available and if not they will create a new one.

This is due to the following bug https://bugs.launchpad.net/nova/+bug/856764