f41e3c220c
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: I2194c61fa9e9bdb32d252284eea1864151d9eef7 Closes-Bug: #1690159
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/Manila
- Developer docs: https://docs.openstack.org/developer/manila
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://github.com/openstack/manila.git
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/manila