Destroy of AWS IPI skips EFS File System

IBM / cloud-pak-deployer

Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.

https://ibm.github.io/cloud-pak-deployer/

Apache License 2.0

132 stars 67 forks source link

Destroy of AWS IPI skips EFS File System #534

Closed Alan111S closed 10 months ago

Alan111S commented 11 months ago

Describe the bug Destroyed an AWS Self Managed Cluster but the AWS EFS FileSystem was not destroyed

To Reproduce Steps to reproduce the behavior: Execute "./cp-deploy.sh env destroy --confirm-destroy"

Expected behavior All Cluster Assets are deleted including the file system

Screenshots The AWS EFS File System still exists

Alan111S commented 11 months ago

I also found that on a destroy the Network Interfaces (eni-XXXXXXX) couldn't destroy because they were still attached as EFS mount points. I manually detached the mount points and the destroy command completed. But the EFS file system was still not destroyed.