Bug 2030379

Summary:	Namespace left orphaned after destroying the cluster
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Thuy Nguyen <thnguyen>
Component:	Cluster Lifecycle	Assignee:	Jian Qiu <jqiu>
Status:	CLOSED ERRATA	QA Contact:	Hui Chen <huichen>
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	unspecified
Version:	rhacm-2.4.z	CC:	crizzo, ecai, wliu1, yuhe
Target Milestone:	---	Flags:	bot-tracker-sync: rhacm-2.4.z+
Target Release:	rhacm-2.4.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-03 06:59:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thuy Nguyen 2021-12-08 15:50:50 UTC

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:

Comment 1 Wei Liu 2021-12-14 01:46:27 UTC

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

Comment 2 Thuy Nguyen 2022-01-11 15:00:23 UTC

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.

Comment 3 Thuy Nguyen 2022-02-09 21:32:10 UTC

Verified on 2.4.2-RC2

Comment 9 errata-xmlrpc 2022-03-03 06:59:24 UTC

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