From cinder code, we know that volume delete operation could be classify into three categories; 1. General delelte: delete volumes that are in the status of available, error, error_restoring, error_extending. 2. Force delete: delete volumes that are in the status of extending, attaching, detaching, await-transfering, backing or restoring. 3. Others: volumes that are attached or in the progress of migrate operation can't be force deleted. We know that volume's status in attaching/detaching also means that the volume is "in-use", not only in "attached" status and in the progress of volume migration. Cinder force delete sometimes can delelte "in-use" volumes, and sometimes can not deleted "in-use" volumes. My question is as follows: 1. Do you think volume force delete operation should not apply to the volume being used? eg. Should attaching/detaching/backing volume can't be force delete ?
From: yunlingz...@hotmail.com To: openstack-dev@lists.openstack.org Subject: [openstack-dev][Cinder]Do you think volume force delete operation should not apply to the volume being used? Date: Mon, 17 Feb 2014 13:13:45 +0000 Hi stackers: I found that volume status become inconsistent (nova volume status is attaching, verus cinder volume status is deleted) between nova and cinder when doing volume force delete operation on an attaching volume. I think volume force delete operation should not apply to the volume being used, which included the attached status of attaching, attached and detached. How do you think? thanks
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
