Back to bug 1017716

Who When What Removed Added
RHEL Program Management 2013-10-10 11:42:04 UTC Target Release --- 4.0
Eric Harney 2013-10-10 14:25:23 UTC CC dron
Assignee rhos-maint eharney
Summary cinder: cinder-volumes do not start if it cannot mount gluster cinder-volume service does not start if it cannot mount gluster
Flags needinfo?(dron)
Dafna Ron 2013-10-10 14:38:13 UTC Flags needinfo?(dron)
Eric Harney 2013-11-20 14:42:21 UTC Status NEW MODIFIED
Fixed In Version openstack-cinder-2013.2-2.el6ost
Ayal Baron 2013-12-01 10:21:45 UTC CC abaron
errata-xmlrpc 2013-12-04 21:10:43 UTC Status MODIFIED ON_QA
Don Domingo 2013-12-10 03:15:33 UTC CC ddomingo
Flags needinfo?(eharney)
Eric Harney 2013-12-10 19:54:08 UTC Doc Text Cause: Failure to initialize a Cinder volume driver would cause the cinder-volume service to fail at startup.

Consequence: cinder-volume service is not accessible ; a failure in one volume driver makes other volume drivers in a multi-backend scenario unavailable.

Fix: Cinder now marks a backend as uninitialized and disables requests to it if it cannot be initialized properly.

Result: Volume driver init failures only affect that driver and not the whole cinder-volume service.
Flags needinfo?(eharney)
Dafna Ron 2013-12-12 12:39:08 UTC Status ON_QA ASSIGNED
Eric Harney 2013-12-12 15:05:28 UTC Flags needinfo?(dron)
Dafna Ron 2013-12-12 15:10:59 UTC Flags needinfo?(dron)
Eric Harney 2013-12-16 15:23:28 UTC Blocks 1043547
Eric Harney 2013-12-16 15:26:01 UTC Status ASSIGNED ON_QA
Scott Lewis 2013-12-16 18:40:47 UTC Target Milestone --- rc
Martin Lopes 2013-12-18 01:49:06 UTC CC mlopes
Doc Text Cause: Failure to initialize a Cinder volume driver would cause the cinder-volume service to fail at startup.

Consequence: cinder-volume service is not accessible ; a failure in one volume driver makes other volume drivers in a multi-backend scenario unavailable.

Fix: Cinder now marks a backend as uninitialized and disables requests to it if it cannot be initialized properly.

Result: Volume driver init failures only affect that driver and not the whole cinder-volume service.
Previously, a failure in the Block Storage volume driver initialization process resulted in 'cinder-volume' service failure at startup.
Consequently, the 'cinder-volume' service was inaccessible, and a failure in one volume driver resulted in other volume drivers being unavailable, in a multiple-backend scenario.
With this update, Block Storage now marks an uninitialized backend and disables requests to it. Volume driver initialization failures now only affect the driver, and not the entire 'cinder-volume' service.
errata-xmlrpc 2013-12-19 17:31:39 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:27:27 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:27:27 UTC
Perry Myers 2016-04-26 13:50:00 UTC CC pmyers

Back to bug 1017716