Description of problem: Leaked namespaces after deleting hypershift deployment Version-Release number of selected component (if applicable): 2.6.0-DOWNSTREAM-2022-07-27-06-01-34 How reproducible: Steps to Reproduce: 1. Create hypershift deployment object on aws successfully 2. Delete the object created in step 1 Actual results: Namespaces created for hypershift deployment are leaked after deleting the hypershift deployment Expected results: Additional info: ``` # oc get ns | grep hs0 hs0-ns Active 72m klusterlet-hs0-7rwk5 Active 70m ```
G2Bsync 1222830659 comment thuyn-581 Mon, 22 Aug 2022 19:37:04 UTC G2BSync - Validated on FC7.
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 (Moderate: Red Hat Advanced Cluster Management 2.6.0 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:6370