Allow c-vol backends to start when some backends fail to load
Currently, if a c-vol backend fails to load due to an error in
the module startup process (like a volume driver's __init__ or
dependency import failure), the c-vol process halts completely.
Instead, catch that backend failure, log it, and allow other
backends in enabled_backends to still start up and run.
Note that this is not applicable for failures that allow
drivers to load and remain "uninitialized" -- this is for
failures that occur prior to that point.
Reviewed: https:/ /review. openstack. org/225982 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=8e69447d7b9 efc23a0695edbbb 55bfbd845a99d8
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8e69447d7b9efc2 3a0695edbbb55bf bd845a99d8
Author: Eric Harney <email address hidden>
Date: Mon Sep 21 14:29:19 2015 -0400
Allow c-vol backends to start when some backends fail to load
Currently, if a c-vol backend fails to load due to an error in
the module startup process (like a volume driver's __init__ or
dependency import failure), the c-vol process halts completely.
Instead, catch that backend failure, log it, and allow other
backends in enabled_backends to still start up and run.
Note that this is not applicable for failures that allow
drivers to load and remain "uninitialized" -- this is for
failures that occur prior to that point.
Closes-Bug: #1497413
Change-Id: If183b9e3d21777 cddf713c2dc88dc 80ae7cfe01d