I'm guessing that you are probably using multiple cinder-volume services to manage the glusterfs volumes. If this is the case, and you didn't set 'host' in cinder.conf to a common name between the cinder-volume services then you can end up in a case where you can't delete a volume because the registered 'host' is offline or no longer around.
On Tue, Oct 27, 2015 at 12:43 AM Matt Riedemann <[email protected]> wrote: > > > On 6/9/2015 11:28 AM, Jesse Keating wrote: > > We've used > > > https://github.com/snemetz/openstack-scripts/blob/master/cinder-volume-delete.txt > > with apparent success to delete stuck volumes. > > > > > > - jlk > > > > On Tue, Jun 9, 2015 at 6:37 AM, Alvise Dorigo <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi, > > I've a cinder volume which is permanently in "deleting" state. I > > cannot retrace the full history of actions that brought to this > > scenario. What I cat reporto is that > > > > 1. Cinder is backed by GlusterFS mounted with the glusterfuse, > > 2. a "cinder delete" (or "cinder force-delete" as admin) doesn't > > produce any effect, > > 3. In the api.log, scheduler.log and volume.log I do not see any > > useful information but this: > > > > api.log-20150607:2015-06-05 14:45:20.956 17383 <tel:20.956%2017383> > > INFO eventlet.wsgi.server [req-bed01706-77ff-48bb-b12c-a0ccdcfd2e25 > > d7b3d4f7d20444adb7fda140553c25bf 3beba6dd3f2648378263bc04d9c205fa - > > - -] 192.135.16.31,192.168.60.21 - - [05/Jun/2015 14:45:20] "DELETE > > > > /v1/3beba6dd3f2648378263bc04d9c205fa/volumes/b056b016-8337-4e64-9069-6c84ab242152 > > HTTP/1.1" 400 338 0.053790 > > > > > > (the verbosity and debug are ON of course). > > > > This is not a single event... unfortunately more that one volume > > cannot be deleted and we're, so far, unable to understand why. > > > > My question is if a manual procedure (operating on the relevant > > cinder's tables) which gracefully cleans things up (which is not a > > trivial "delete from volume where id='...'") exists. > > > > Thanks, > > > > Alvise > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > <mailto:[email protected]> > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > FYI, there is an effort going on here [1] to add a force volume > attachment removal command to nova-manage. Operator input on that change > would be valuable. > > [1] https://review.openstack.org/#/c/184537/ > > -- > > Thanks, > > Matt Riedemann > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
