Description of the problem: Namespace left orphaned after destroying the cluster Release version: ACM 2.4.1 Operator snapshot version: OCP version: 4.9.4 Browser Info: Firefox 78.15.0esr (64-bit) Steps to reproduce: 1. Provision a cluster on AWS in ACM UI 2. Destroy the cluster provisioned in step 1 Actual results: Cluster deprovision completed, yet the cluster namespace remained Expected results: Additional info:
Hi, @thnguyen I try this with `2.4.1-SNAPSHOT-2021-12-07-05-45-07`, but I cannot reproduce this problem, I follow the below steps 1. Provision an ocp 4.9.10 on AWS in ACM UI 2. After the cluster is provisioned, then destroy the cluster both the cluster and its namespace are deleted Would you try this again, and if the problem exists, would you share your env to me, thanks
Hi, I have tried the following scenarios: 1. Destroy the cluster which was provisioned successfully > the namespace is removed after destroying 2. Destroy the cluster which was provisioned failed or of which provisioning is in progress > the namespace is left orphaned after destroying >> reported in this issue.
Verified on 2.4.2-RC2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.4.2 security updates and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0735