-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.13.z, 4.12.z, 4.14.z
-
Important
-
No
-
Proposed
-
False
-
Description of problem:
ROSA HyperShift clusters are failing to uninstall with the HCCO failing to cleanup the image-registry
Version-Release number of selected component (if applicable):
So far, observed on 4.12.22 and 4.12.24
How reproducible:
Uncertain
Steps to Reproduce:
Uninstall a ROSA HCP cluster
Actual results:
HCCO Logs: {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Ensuring image registry storage is removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Setting management state for registry operator to removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Ensuring ingress controllers are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"There are no ingresscontrollers, nothing to do","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Ingress controllers are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Ensuring load balancers are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Load balancers are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Ensuring persistent volumes are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"There are no more persistent volumes. Nothing to cleanup.","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"} {"level":"info","ts":"2023-07-13T01:28:14Z","msg":"Persistent volumes are removed","controller":"resources","object":{"name":""},"namespace":"","name":"","reconcileID":"48640526-592d-4306-8038-5204cdd6628b"}
and the hostedcluster has this status condition:
- lastTransitionTime: "2023-07-12T17:04:48Z" message: 'Remaining resources: image-registry,ingress-controllers,loadbalancers' observedGeneration: 3 reason: RemainingCloudResources status: "False" type: CloudResourcesDestroyed
which is unexpected because truly only the image-registry is remaining as can be seen through the HCCO logs
Expected results:
Primarily, that the image-registry can successfully cleanup, but secondarily that the associated status condition is accurate
Additional info: