So during VM create the libvirt driver always starts the instance paused, then turns active after the neutron event comes in. That is expected.
sounds like the power state sync races the create somehow, we do have instance locks in there to try and prevent that and power state sync usually skips instance that are busy doing some task.
So during VM create the libvirt driver always starts the instance paused, then turns active after the neutron event comes in. That is expected.
sounds like the power state sync races the create somehow, we do have instance locks in there to try and prevent that and power state sync usually skips instance that are busy doing some task.