manila/releasenotes/notes
Goutham Pacha Ravi 35648819aa Fix force-delete on snapshot resource
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
2016-04-01 18:33:26 +00:00
..
.placeholder Add reno for release notes management 2015-11-26 07:16:03 +01:00
add-export-locations-api-6fc6086c6a081faa.yaml Implement export location metadata feature 2016-01-15 12:29:12 +02:00
add-tegile-driver-1859114513edb13e.yaml Add share driver for Tegile IntelliFlash Arrays 2016-03-03 01:13:54 -08:00
manage-unmanage-snapshot-bd92164472638f44.yaml Manage and unmanage snapshot 2016-02-18 04:09:05 -05:00
share-replication-81ecf4a32a5c83b6.yaml Share Replication API and Scheduler Support 2016-02-11 19:45:37 +00:00
snapshot-force-delete-4432bebfb5a0bbc9.yaml Fix force-delete on snapshot resource 2016-04-01 18:33:26 +00:00