Created attachment 1795764 [details] Failed Job Description of the problem: Customer attempted install of OCP 4.7 cluster on vSphere 7.0.2 -- install failed. Upon attempt to remove the failed install via the Destroy Cluster functionality on ACM console, cluster-to-be-destroyed sits in perpetual 'Destroying' status. Release version: release-2.2 Operator snapshot version: rhacm-2.2.5 OCP version: Client Version: 4.7.13 Server Version: 4.7.13 Browser Info: Chromium & CLI Steps to reproduce: 1. Log into ACM, go to Cluster Lifecycle. 2. Attempt to create a cluster. Customer has issue present where install is failing on vSphere. 3. Attempt a 'Destroy Cluster' from the Cluster Lifecycle. Actual results: On Cluster Lifecycle page, the "destroyed" cluster will sit in perpetual "Destroying" status. Expected results: Cluster should remove itself fairly quickly from cluster lifecycle page. Current resolve: As kubeadmin, remove the failed namespace. Additional info: More detailed screenshots available via internal email. The issue seems to stem from a failed uninstall job. Since nothing was able to really happen on the backend vSphere install, an error is present with "Object References is Empty"
Created attachment 1795765 [details] Perpetual Failed State on Lifecycle Management
This seems to be a cluster lifecycle issue
This is a known issue in 2.2. Please see https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.2/html/release_notes/red-hat-advanced-cluster-management-for-kubernetes-release-notes#cluster-management-issues, section 1.3.3.12. Process to destroy a cluster does not complete for information on properly cleaning up the kubernetes resources.
G2Bsync 870703050 comment chrisahl Tue, 29 Jun 2021 15:33:07 UTC G2Bsync This is a known issue in 2.2. Please see https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.2/html/release_notes/red-hat-advanced-cluster-management-for-kubernetes-release-notes#cluster-management-issues, section `1.3.3.12. Process to destroy a cluster does not complete` for information on properly cleaning up the kubernetes resources.
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 (Red Hat Advanced Cluster Management 2.2.6 bug fix update), 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/RHBA-2021:3126