yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90306
[Bug 1834659] Fix included in openstack/nova queens-eol
This issue was fixed in the openstack/nova queens-eol release.
** Changed in: nova/queens
Status: Fix Committed => 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/1834659
Title:
Volume not removed on instance deletion
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
Status in OpenStack Compute (nova) stein series:
Fix Released
Status in OpenStack Compute (nova) train series:
Fix Released
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-1748-4f04-9a29-128cf22efcc5 - 130GiB In-use - Attached to None on /dev/vda
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.volume.drivers.hitachi.hbsd.hbsd_fc.HBSDFCDriver
As a note, the hitachi drivers are unsupported as of Pike (see cinder
commit 595c8d3f8523a9612ccc64ff4147eab993493892
Issue was reproduced in a devstack environment runnning the Stein release.
Volume driver used was lvm (devstack default)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1834659/+subscriptions
References