e8f086d0f5
- Deferred deletion would be regular deletion where quota is freed before resource deletion by driver and deletion states are hidden from end-user. Also, everything will be handled by Manila or admin if any error occurs in deletion. - Any error during deferred deletion will put share/snapshot in error_deferrer_deleting state and periodic task will handle it. - count_share_group_snapshot_members_in_share() should not return share instances in deferred deletion states as those shares are hidden from end-user once deferred deleted. Only actual deletion (by driver) will make sure snapshot instance of share instance should be deleted before share instance deletion. partially-implements: bp/deferred-deletion Closes-bug: #2068043 Change-Id: Ie827619d3952d1db69559206b5dfd47efb4cf7b1
11 lines
539 B
YAML
11 lines
539 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When deferred deletion is enabled, Manila will attempt regular deletion.
|
|
While quota is released, and these objects (shares, snapshots) are hidden
|
|
from the user. Any error during deferred deletion will put resource in
|
|
`error_deferred_deleting` state. After that, it will be handled in
|
|
periodic task. Also, Manila will make sure snapshot instances are deleted
|
|
before share instance delete. For more details, please check
|
|
Launchpad `bug 2068043 <https://bugs.launchpad.net/manila/+bug/2068043>`_
|