When deleting an instance, if the network info is empty, we should
refresh the info because we can't be sure the copy of the cache we
have when we fetched the instance to delete is up-to-date, i.e. if
we're racing to delete the server while it's building and the
network info cache was updated in the database after we started the
delete operation and got the instance from the DB, then we could
fail to unplug VIFs.
Reviewed: https:/ /review. opendev. org/660761 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=d4ed0d8b7ad c350e8962df033c 2da892c95561fe
Committed: https:/
Submitter: Zuul
Branch: master
commit d4ed0d8b7adc350 e8962df033c2da8 92c95561fe
Author: Arnaud Morin <email address hidden>
Date: Wed May 22 17:34:20 2019 +0200
Refresh instance network info on deletion
When deleting an instance, if the network info is empty, we should
refresh the info because we can't be sure the copy of the cache we
have when we fetched the instance to delete is up-to-date, i.e. if
we're racing to delete the server while it's building and the
network info cache was updated in the database after we started the
delete operation and got the instance from the DB, then we could
fail to unplug VIFs.
Closes-Bug: #1830081
Change-Id: I99601773406c61 f93002e2f7cbb24 8cf73cef0ab
Signed-off-by: Arnaud Morin <email address hidden>