Red Hat Bugzilla – Bug 980977
[RHS-RHOS] If storage becomes unavailable volume actions fail (error_deleting)
Last modified: 2016-04-26 09:33:37 EDT
Description of problem:
If the storage back end becomes available during volume actions the status in the webUI gets stuck:
test-vol-BZ "stopping gluster volume while creating." 10GB Error_Deleting
I had to go into the database and manually remove the entries to fix the web UI:
mysql --host=localhost --user=root --password=blah
select * from volumes;
select id,host,display_name from volumes
delete from volumes where display_name='test-vol-BZ';
Version-Release number of selected component (if applicable):
I have hit this a couple of different ways so far:
-Power off all gluster nodes during a volume create
-Stop mounted gluster volume, then delete the cinder volume
Steps to Reproduce:
1. Create a new volume on a glusterfs backend
2. On the gluster server run:
# gluster volume stop testvol
3. Attempt to delete the volume from the webUI while the gluster volume is stopped.
4. Restart the gluster volume:
# gluster volume start testvol
The volume status hangs at error_deleting. I get an error message in the webUI saying:
You do not have permission to delete volume: test-vol-BZ
I am able to delete the volume after storage comes back up.
I can see this being problematic when there are connectivity issues and/or if there are split brain issues on the gluster back end.
I believe "cinder force-delete" will allow you to remove the volume rather than manipulating the database.
(In reply to Eric Harney from comment #1)
> I believe "cinder force-delete" will allow you to remove the volume rather
> than manipulating the database.
Eric, regardless of a workaround of using force-delete, in the least the error message is incorrect.
In addition, what happens if the user issues delete again? would that work?