Also important to note, you should check the 'provider_location' column for the volumes in error_deleting, otherwise you may have the space potentially allocated on the backend, but cinder thinking it's deleted. I also like to update 'deleted_at' to "NOW"
On Mon, Jan 5, 2015 at 10:41 AM, Erlon Cruz <sombra...@gmail.com> wrote: > This is usually is related to mis-configuration on the backend driver. For > example, if you create a volume, shutdown the driver to change some > configuration, the backend driver can get confused while trying to delete > the volume or even can't be able to locate the volume in the storage array. > S > > On Mon, Jan 5, 2015 at 3:35 AM, Eli Qiao <ta...@linux.vnet.ibm.com> wrote: > >> >> 在 2015年01月05日 13:02, Punith S 写道: >> >> Hi Eli, >> >> you have to log-in to MySQL cinder database , and try deleting the >> required volume from the volumes table using the id. >> if it fails due to foreign key constraints in volume metadata table, try >> deleting the corresponding volume metadata and then try to delete the >> required volume row. >> >> hi Punith, I did as your suggestion, it works. but is that reasonable >> not to delete a error_deleting even that status keeping for a quite long >> time? >> thanks. >> >> thanks >> >> On Mon, Jan 5, 2015 at 7:22 AM, Eli Qiao <ta...@linux.vnet.ibm.com> >> wrote: >> >>> >>> hi all, >>> how to delete a cinder volume which is in error_deleting status ? >>> I don't find force delete options in 'cinder delete', then how we fix >>> it if we got such situation ? >>> [tagett@stack-01 devstack]$ cinder list >>> >>> +--------------------------------------+----------------+-------------+------+-------------+----------+--------------------------------------+ >>> | ID | Status | Name | >>> Size | Volume Type | Bootable | Attached to | >>> >>> +--------------------------------------+----------------+-------------+------+-------------+----------+--------------------------------------+ >>> | 3e0acd0a-f28f-4fe3-b6e9-e65d5c40740b | in-use | with_cirros | >>> 4 | lvmdriver-1 | true | 428f0235-be54-462f-8916-f32965d42e63 | >>> | 7039c683-2341-4dd7-a947-e35941245ec4 | error_deleting | None | >>> 4 | lvmdriver-1 | false | | >>> | d576773f-6865-4959-ba26-13602ed32e89 | error_deleting | None | >>> 4 | lvmdriver-1 | false | | >>> >>> +--------------------------------------+----------------+-------------+------+-------------+----------+--------------------------------------+ >>> [tagett@stack-01 devstack]$ cinder delete >>> 7039c683-2341-4dd7-a947-e35941245ec4 >>> Delete for volume 7039c683-2341-4dd7-a947-e35941245ec4 failed: Bad >>> Request (HTTP 400) (Request-ID: req-e4d8cdd9-6ed5-4a7f-81de-7f38f2163d33) >>> ERROR: Unable to delete any of specified volumes. >>> >>> -- >>> Thanks, >>> Eli (Li Yong) Qiao >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> -- >> regards, >> >> punith s >> cloudbyte.com >> >> >> _______________________________________________ >> OpenStack-dev mailing >> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> -- >> Thanks, >> Eli (Li Yong) Qiao >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev