One thing I'd be interested in, is on initial server create with the libvirt driver, we have the callback from neutron on VIF plugging that we wait for, I wonder if that same code path is used for resize/migrate/reboot? I'm wondering if we're just getting lucky when things pass that the ports are still attached/associated with the instance on the neutron side after doing a resize/migration. In the reboot case, it might be something completely different, like the guest not coming up/being ready even though the ports are still attached after the reboot.
One thing I'd be interested in, is on initial server create with the libvirt driver, we have the callback from neutron on VIF plugging that we wait for, I wonder if that same code path is used for resize/ migrate/ reboot? I'm wondering if we're just getting lucky when things pass that the ports are still attached/associated with the instance on the neutron side after doing a resize/migration. In the reboot case, it might be something completely different, like the guest not coming up/being ready even though the ports are still attached after the reboot.