if gluster cannot be mounted cinder-volumes fail to start

Bug #1237948 reported by Dafna Ron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

I configured cinder to work with gluster as backend and due to some issue mounting gluster cinder-volumes could not be started

I am not sure this is a correct behaviour since if a service is down we need to manually start it (which is not nice to do in a large scale deployment with lots of cinder servers).

I think that the best practice for this would be to allow the service to start and try to mount every X time so that when the storage is available it will automatically connect - so not needing manual interference from the admin.

Tags: glusterfs
Revision history for this message
Avishay Traeger (avishay-il) wrote :

I would suggest making this generic - the driver's do_setup implementation can raise some "unavailable" exception, and the manager can then retry. I saw at least one other driver fix this issue, and it exists in others as well - the fix should be made generic.

tags: added: drivers glusterfs
tags: removed: drivers glusterfs
Revision history for this message
Eric Harney (eharney) wrote :

I think this was fixed when the driver is_initialized changes went in.

tags: added: glusterfs
Revision history for this message
Eric Harney (eharney) wrote :

This was fixed with the changes to require drivers to be initialized for operations to occur.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.