Ask Your Question

Revision history [back]

Make sure and check the controller host /var/log/upstart directory for logs that have activity and look for things like authentication failures on the API. Also I have ran into this issue numerous times just to find that there weren't enough CPU or storage on the only compute node I had at the time. I have since added several more and beefed up the drives and the problem went away.

Lastly, another issue I had that caused the same error message you're seeing, was that Openstack was attempting to put the server on my controller since the controller also had nova-compute installed. So what I did was setup an aggregate host list and an availability zone so that only compute nodes and storage nodes were in the zone, this forces openstack to use one of the compute nodes as the VM host machine and won't ever let it put it onto the controller.

Good luck

Make sure and check the controller host /var/log/upstart directory for logs that have activity and look for things like authentication failures on the API. Also I have ran into this issue numerous times just to find that there weren't enough CPU or storage on the only compute node I had at the time. I have since added several more and beefed up the drives and the problem went away.

Lastly, another issue I had that caused the same error message you're seeing, was that Openstack was attempting to put the server VM on my controller since the controller also had nova-compute installed. So what I did was setup an aggregate host list and an availability zone so that only compute nodes and storage nodes were in the zone, this forces openstack to use one of the compute nodes as the VM host machine and won't ever let it put it onto the controller.

Good luck