OpenStack file share deletion fails when it's triggered shortly after deleting a snapshot that has a clone
Applies to
- ONTAP 9
- OpenStack
- Manila
- Deleting an OpenStack File Share shortly after deleting a snapshot that has a clone
Example:
- Create a share SHARE-A
- Create a snapshot SNAPSHOT-A of SHARE-A
- Create a share SHARE-B from SNAPSHOT-A
- Delete SNAPSHOT-A
- Delete SHARE-A
Issue
- File share deletion fails with
error_deletingin the status of the file share - Error in Manila service log:
ERROR oslo_messaging.rpc.server [F] [None req-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - - - -] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15894:Failed to delete volume "share_XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX" in Vserver "<SVM_NAME>" because it has one or more clones. Use the "volume clone show -parent-vserver <SVM_NAME> -parent-volume share_XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX" command to list clones, and either delete or split the clones and retry the operation. Use "volume clone split start -vserver <vserver name> -flexclone <clone name>" to split clones. Use "volume delete -vserver <vserver name> -volume <clone name>" to delete clones.
