yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69367
[Bug 1733736] [NEW] reclaim_instance_interval
Public bug reported:
Description
When set reclaim_instance_interval > 0, and we delete an instance which boot from volume with delete_on_termination set as true.
After reclaim_instance_interval time pass, all volumes boot instance will with state: attached and in-use, but attached instances was deleted.
Steps to reproduce
1. set reclaim_instance_interval = 60
2. create a bootable volume
3. boot instance with created bootable volume
4. delete instance, and wait 60 seconds
Expected result
Previous test bootable volume was deleted after
reclaim_instance_interval seconds.
Actual result
Previous test bootable volume was in state attached and in-use, attached
with deleted instance.
** Affects: nova
Importance: Undecided
Assignee: Li Xipeng (lixipeng)
Status: In Progress
** Description changed:
Description
- ===========
When set reclaim_instance_interval > 0, and we delete an instance which boot from volume with delete_on_termination set as true.
After reclaim_instance_interval time pass, all volumes boot instance will with state: attached and in-use, but attached instances was deleted.
Steps to reproduce
- ==================
1. set reclaim_instance_interval = 60
2. create a bootable volume
3. boot instance with created bootable volume
4. delete instance, and wait 60 seconds
-
Expected result
- ===============
Previous test bootable volume was deleted after
reclaim_instance_interval seconds.
-
Actual result
- =============
Previous test bootable volume was in state attached and in-use, attached
with deleted instance.
** Changed in: nova
Assignee: (unassigned) => Li Xipeng (lixipeng)
--
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/1733736
Title:
reclaim_instance_interval
Status in OpenStack Compute (nova):
In Progress
Bug description:
Description
When set reclaim_instance_interval > 0, and we delete an instance which boot from volume with delete_on_termination set as true.
After reclaim_instance_interval time pass, all volumes boot instance will with state: attached and in-use, but attached instances was deleted.
Steps to reproduce
1. set reclaim_instance_interval = 60
2. create a bootable volume
3. boot instance with created bootable volume
4. delete instance, and wait 60 seconds
Expected result
Previous test bootable volume was deleted after
reclaim_instance_interval seconds.
Actual result
Previous test bootable volume was in state attached and in-use,
attached with deleted instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1733736/+subscriptions
Follow ups