[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@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Force deletion in Cinder Hi, 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 Lisa
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 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li@intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@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@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Force deletion in Cinder Hi, 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 Lisa
Hi Liang, Can you explain the relationship to horizon. The patches address an issue where cinder still believes the volume is attached to a VM but the VM no longer exists. II am not seeing the horizon connection here. Brent From: Fang, Liang A [mailto:liang.a.fang@intel.com] Sent: Wednesday, November 21, 2018 8:26 PM To: Li, Xiaoyan <xiaoyan.li@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] [StarlingX] Force deletion in Cinder 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 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li@intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@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@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Force deletion in Cinder Hi, 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 Lisa
Hi Brent The bug reported to horizon is: When user try to remove the attachment by click the button "Manage Attachments" for the orphan volume, GUI just shows: "Error: Unable to retrieve volume information. ", and cannot open the "Manage Attachments" dialog. Regards Liang From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Thursday, November 22, 2018 10:58 AM To: Fang, Liang A <liang.a.fang@intel.com>; Li, Xiaoyan <xiaoyan.li@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Hi Liang, Can you explain the relationship to horizon. The patches address an issue where cinder still believes the volume is attached to a VM but the VM no longer exists. II am not seeing the horizon connection here. Brent From: Fang, Liang A [mailto:liang.a.fang@intel.com] Sent: Wednesday, November 21, 2018 8:26 PM To: Li, Xiaoyan <xiaoyan.li@intel.com<mailto:xiaoyan.li@intel.com>>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] [StarlingX] Force deletion in Cinder 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 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li@intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@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@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Force deletion in Cinder Hi, 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 Lisa
participants (3)
-
Fang, Liang A
-
Li, Xiaoyan
-
Rowsell, Brent