commit f41e3c220c209aab35691e95a6db3a8ac303ea09
Author: Thomas Bechtold <email address hidden>
Date: Fri May 12 15:54:48 2017 +0200
Retry backend initialization
Since commit 4b87f6f40d1f09b4, exceptions in the init_host() call (which is
called for every backend) are catched and backends might end up
uninitialized and unusable. This might be okish (but is not good) in a
multi-backend scenario but is definitely wrong in a single backend scenario.
In that case, the manila-share process would successfully start but the
backend would never be usable.
So retry to initialize the driver for every backend in case there was an error
during initialization. That way even a temporary broken backend can be
initialized later without restarting manila-share.
Reviewed: https:/ /review. openstack. org/464205 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=f41e3c220c2 09aab35691e95a6 db3a8ac303ea09
Committed: https:/
Submitter: Jenkins
Branch: master
commit f41e3c220c209aa b35691e95a6db3a 8ac303ea09
Author: Thomas Bechtold <email address hidden>
Date: Fri May 12 15:54:48 2017 +0200
Retry backend initialization
Since commit 4b87f6f40d1f09b4, exceptions in the init_host() call (which is
called for every backend) are catched and backends might end up
uninitialized and unusable. This might be okish (but is not good) in a
multi-backend scenario but is definitely wrong in a single backend scenario.
In that case, the manila-share process would successfully start but the
backend would never be usable.
So retry to initialize the driver for every backend in case there was an error
during initialization. That way even a temporary broken backend can be
initialized later without restarting manila-share.
Change-Id: I2194c61fa9e9bd b32d252284eea18 64151d9eef7
Closes-Bug: #1690159