[Openstack] nova drop port after VMs was evacuated through host-evacuate and failed compute was started again
Yura Poltoratskiy
yurapoltora at gmail.com
Mon Jul 18 10:36:02 UTC 2016
Hello.
Recently my compute was failed and I run host-evacuate, the VMs was started
properly, but after failed compute was started again, nova was dropped
ports of VMs which was evacuated with next log in nova-compute.log:
2016-07-15 03:29:59.013 4617 INFO nova.network.neutronv2.api
[req-c76160e4-4a29-4f78-85e4-ab5b1dc08dd4 - - - - -] [instance:
eb6a628a-242d-4a3c-b88f-5189e06b3d97] Port
46cae1d0-b894-419f-ac8f-56c85c74b184 from network info_cache is no longer
associated with instance in Neutron. Removing from network info_cache.
Is this a bug?
Which is the right scenario to properly boot failed compute?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160718/29aa7348/attachment.html>
More information about the Openstack
mailing list