Troubleshooting an installation of Nova is similar to the ones described in the previous chapters. While we have still not spun up an instance, let's take a look at some failure scenarios when we do spin an instance up and it refuses to come up.
Here are some of the preliminary checks:
If the authentication was not a problem, we follow the following procedure:
nova-api.log
on the controller node to check whether the request was properly received. If the request was not properly handled, you will see the reason here.nova list
command and note down the instance ID of the system.nova console-log <uuid of the VM>
command to see the logs.These logs should point you to the right direction. If the system is stuck at building or scheduling, and the VM has not begun to be built yet, then there can be two possible reasons:
The first log file to be checked will be of the nova scheduler; then check nova-compute.log
on the compute node. These are general guidelines and further troubleshooting may be needed on the hypervisor side.