[Starlingx-discuss] [StarlingX] Force deletion in Cinder

Fang, Liang A liang.a.fang at intel.com
Thu Nov 22 01:26:14 UTC 2018

Hi Lisa

The core Eric Harney from redhat has already abandoned the review of this patch.
In the meanwhile, a bug for horizon was created: https://bugs.launchpad.net/horizon/+bug/1794661

From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com]
Sent: Thursday, November 22, 2018 8:50 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder

Sorry, updated the subject.

From: Li, Xiaoyan
Sent: Thursday, November 22, 2018 8:49 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Force deletion in Cinder


This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder.
This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted.

I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist.
Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted.
Fang Liang also did such test, it works.

So I think we can abandon this patch. Any objections?

Best wishes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181122/38737393/attachment-0001.html>

More information about the Starlingx-discuss mailing list