yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77467
[Bug 1734025] Re: cleanup running deleted instance with reap failed with none token context
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Li Xipeng (lixipeng)
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
Assignee: (unassigned) => huanhongda (hongda)
** Changed in: nova/pike
Importance: Undecided => Medium
--
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/1734025
Title:
cleanup running deleted instance with reap failed with none token
context
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) pike series:
In Progress
Bug description:
Description
When zombied instances appear(You can also see bug https://bugs.launchpad.net/nova/+bug/911366),
set running_deleted_instance_poll_interval = 60 and running_deleted_instance_action = reap, then nova-compute service will clear those zombied instances, but if those instances is boot from volume or had volumes attached. After clear, zombied instances cleared, but volumes with attached status exist, and if those volumes are bootable and used to boot volume and set deleted_on_termination=True, thoses volume will still exist and in attached status but instance did not exist.
Steps to reproduce
1. set running_deleted_instance_poll_interval=60 and running_deleted_instance_action = reap.
2. update an running instance status to deleted.
3. restart nova-compute service and wait 60 seconds.
Expected result
Previous test bootable volume was deleted and volumes attached to
zombied instances ware detached.
Actual result
Previous test bootable volume was in state attached and in-use,
volumes attached to zombied instances ware in-use and attached to
those zombied instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1734025/+subscriptions
References