-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.13.z, 4.12.z, 4.14.z
-
Important
-
No
-
Hypershift Sprint 241
-
1
-
Proposed
-
False
-
Description of problem:
Very similar to OCPBUGS-14611 - not all LoadBalancer services can be cleaned up by default if the customer has installed something like AWS Load Balancer Operator to provision then (i.e. anything other than the in-tree cloud-controller-manager supported ones currently)
Version-Release number of selected component (if applicable):
N/A
How reproducible:
100%
Steps to Reproduce:
1. Install a custom LoadBalancer service operator, such as AWS Load Balancer Operator - https://docs.openshift.com/container-platform/4.13/networking/aws_load_balancer_operator/understanding-aws-load-balancer-operator.html 2. Provision a LoadBalancer service using the AWS Load Balancer Operator 3. Uninstall the cluster
Actual results:
Uninstall gets stuck as the HCCO never gets to a state where all LoadBalancer services are deleted
Expected results:
The uninstall completes, like with OCPBUGS-14611 the finalizers could be directly removed automatically
Additional info:
- is related to
-
OCPBUGS-14611 Uninstallation blocked by dangling PersistentVolume
- Closed