Revision history [back]

I'm pretty sure this bug is related to your issue:

To fix, you can either apply this patch or boot an instance with a 0GB root disk flavor to this host. This will cache the base image and prevent this bug from appearing. Make sure you use the same image that you wish to boot your other flavors from.

If you choose to do the latter, you can select the host to which your instance will boot by including --availability-zone in your nova boot command. For example:

nova boot --flavor 1 --image 95e50545-3452-4ee9-be32-cfd65ee0ac6f --availability-zone nova:$COMPUTE_HOST instance-name

Where $COMPUTE_HOST is the hostname of the compute host as defined in the nova.compute_nodes table.