-
Bug
-
Resolution: Done
-
Critical
-
ACM 2.5
Problem
When deleting an azure hypershiftDeployment that was PROGRESS=COMPLETED, along with an AWS hypershiftDeployment, the Azure manifestWork was removed, the hypershiftDeployment was removed, but the Azure HC and NP still exist on the system... ManifestWork did not remove them..
I had two completed clusters (AWS & Azure). I ran an "oc delete hypershiftDeployment aws azure" I could see Azure and AWS shows Manifestwork=Removing, and Azure showed Infra=Destroying, but the HC and NP were left behind, along with all its control plane pods.
Investigation
Because the infra=removing step for Azure ran, the resource group for the cluster was gone and there was no NODE objects left behind in Azure (infra cleanup was good), but the NP and HC + pods were still present on the HostingCluster, and there was NO manifestWork any more.
I was also provisioning a NEW AWS hypershiftDeployment when I deleted the old AWS & Azure.