Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691324 - Volumes remain in the attached state even when the instance is already deleted
Summary: Volumes remain in the attached state even when the instance is already deleted
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Linux
Target Milestone: ---
: ---
Assignee: nova-maint
QA Contact: nova-maint
Depends On:
Blocks: 1691839 1691840 1691842 1691844
TreeView+ depends on / blocked
Reported: 2019-03-21 12:07 UTC by Shailesh Chhabdiya
Modified: 2019-04-11 11:49 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1691839 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Shailesh Chhabdiya 2019-03-21 12:07:12 UTC

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.

Extra info:

The fix is available in upstream pike release [1]

Can we backport it to OSP10?


Comment 1 Alan Bishop 2019-03-21 12:11:13 UTC
Volume attachment state is controlled by nova.

Note You need to log in before you can comment on or make changes to this bug.