Volume not removed on instance deletion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
François Palin | ||
Queens |
Fix Released
|
Undecided
|
Unassigned | ||
Rocky |
Fix Released
|
Undecided
|
Unassigned | ||
Stein |
Fix Released
|
Undecided
|
Unassigned | ||
Train |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description
===========
When we deploy a non-ephemeral instance (i.e. Creating a new volume), and
indicate "YES" in "Delete Volume on Instance delete",then delete the
instance, and volume driver terminate connection in cinder takes too long
to return, the volume is not removed.
The volume status remains as "In-use" and "Attached to None on /dev/vda".
For example:
abcfa1db-
Steps to reproduce
==================
Please refer to this bug comment #2 below
Expected result
===============
Volume gets removed
Actual result
=============
Volume remains attached
Environment
===========
Issue was initially reported downstream against Newton release (see
comment #1 below). Customer was using hitachi volume driver:
volume_driver = cinder.
As a note, the hitachi drivers are unsupported as of Pike (see cinder
commit 595c8d3f8523a96
Issue was reproduced in a devstack environment runnning the Stein release.
Volume driver used was lvm (devstack default)
this is a clone of the following downstream bug: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1622072