35648819aa
When using snapshot-delete API, if the share driver logs an exception, the status of the snapshot is set to 'error_deleting'. If an administrator wants to remove this snapshot, he/she would expect to use the snapshot-force-delete API. However, if the share driver still cannot delete the resource, it will remain in 'error_deleting' state; leaving the administrator with no choice but to resort to making changes to the snapshot record in Manila's database. Propagate the force flag to the share manager and log driver exceptions, while ignoring them to obliterate the snapshot on Manila's database if the delete operation is forced. Also fix data being sent in create/delete snapshot driver interfaces and refactor corresponding unit tests. Change-Id: Ic2494e1f9eb9104f96ef3a50f12d0f304735ee4f Closes-Bug: #1560119
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: http://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 http://bugs.launchpad.net/manila