-
Bug
-
Resolution: Unresolved
-
Normal
-
4.16
-
Important
-
None
-
False
-
-
During cluster or node deletion via the SiteConfig CR the BareMetalHost CR may get stuck in the deleting state. This fix ensures that the deletion order is correct to avoid this condition. This fix requires GitOps operator 1.13 or later.
-
Bug Fix
-
In Progress
-
This is a clone of issue OCPBUGS-46071. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-42945. The following is the description of the original issue:
—
Description of problem:
BMH and NS of the SpokeCluster are freeze in Terminating/Deprovisioning State
Version-Release number of selected component (if applicable):
OCPv4.16.3 openshift-gitops-operator.v1.13.1 topology-aware-lifecycle-manager.v4.16.1 multicluster-engine.v2.6.1 local-storage-operator.v4.16.0-202407190036 advanced-cluster-management.v2.11.1
How reproducible:
60-70%
Steps to Reproduce:
1.Create SiteConfig of the Spoke 2.Commit the SiteConfig to Git 3.Allow ArgoCD application to sync 4.BMH enters Inspecting state 5.Now remove the SiteConfig from kustomize.yaml 6.Now ArgoCD application gets to sync 7.BMH and NS are in Deprovisioning/Terminating State longer than 15 minutes.
Actual results:
BMH and NS of the Spoke are in Deprovisioning/Terminating State longer than 15 minutes.
Expected results:
Expectations are that BMH and NS of the Spoke to be removed
Additional info:
- blocks
-
OCPBUGS-47798 BareMetalHost CR fails to delete on cluster cleanup
- POST
- clones
-
OCPBUGS-46071 BareMetalHost CR fails to delete on cluster cleanup
- Verified
- is blocked by
-
OCPBUGS-46071 BareMetalHost CR fails to delete on cluster cleanup
- Verified
- is cloned by
-
OCPBUGS-47798 BareMetalHost CR fails to delete on cluster cleanup
- POST
- links to