Why can't I delete an SVM on my FSx for ONTAP file system?

Resolution

Identify why the SVM failed to delete

To view the reason for the deletion failure, run the following AWS Command Line Interface (AWS CLI) command:

$ aws fsx describe-storage-virtual-machines --storage-virtual-machine-ids  svm-123456789 --query 'StorageVirtualMachines[*].{Lifecycle:Lifecycle,LifecycleTransitionReason:LifecycleTransitionReason'}
[
    {
        "Lifecycle": "MISCONFIGURED",
        "LifecycleTransitionReason": {
            "Message": "Amazon FSx is unable to delete the storage virtual machine because ..."
        }
    }
]

Note: If you receive errors when you run AWS CLI commands, see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.

Or, use the Amazon FSx console to identify the reason for the failed deletion. For more information, see Identifying failed deletions.

Common causes for SVM deletion failure

The following are common causes and solutions for the failed deletion:

• The default tags Key: AmazonFSx and Value: ManagedByAmazonFSx that are associated with your route tables are removed. If these tags aren't present, then recreate the tags. Then, delete the SVM.
• You tried to delete an SVM that's part of an SVM peer or transition peer relationship. Delete each SVM peer relationship, and then delete the SVM.
• You tried to delete an SVM that has a SnapMirror relationship. Delete the SnapMirror relationship, and then delete the SVM.
• You tried to delete an SVM that has a logical interface (LIF) with Kerberos turned on. Turn off Kerberos on the LIF, and then delete the SVM.
• When you join FSx for ONTAP SVMs to your AWS Directory Service for Microsoft Active Directory or self-managed Microsoft Active Directory, the SVMs create a computer object in your Active Directory. In some cases, you must manually unjoin an SVM from your Active Directory. Use the NetApp ONTAP CLI to unjoin the SVM.

For more information, see You can't delete a storage virtual machine or volume.