yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #83871
[Bug 1414895] Re: failed compute node didn't delete instance's path directory in init_host
** Changed in: nova/rocky
Status: In Progress => Fix Released
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova/queens
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1414895
Title:
failed compute node didn't delete instance's path directory in
init_host
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) queens series:
Fix Released
Status in OpenStack Compute (nova) rocky series:
Fix Released
Bug description:
It will do clean for evacuated instances in method init_host in nova/compute/manager.py we restart a failed compute node .
while using volume-backend shared-storage (like ceph) , nova leaves instance path directory in failed compuet node.
The root cause is that we only passed argument "destroy_disks" to driver.destroy, the value will be true while using ceph.
then will not delete instance path .
This may lead live-migration instance failure with exeption DestinationDiskExists
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1414895/+subscriptions
References