-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13.z, 4.12.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
Rejected
-
Hypershift Sprint 234, Hypershift Sprint 235
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Deletion of a LoadBalancer can get blocked because a service endpoint still points to it, this results in a blocked uninstallation process.
kube controller manager of MC:
I0316 13:18:36.967329 1 event.go:294] "Event occurred" object="ocm-staging-22ad0p03svv24fgfvi14alf4cv4c8jn2-perf-znl-0045/private-router" fieldPath="" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message=< Error syncing load balancer: failed to delete load balancer: error deleting load balancer "aa02d38c1ce264a5691a0bbfcbe64f37": ResourceInUse: Load balancer 'arn:aws:elasticloadbalancing:us-east-2:805206591657:loadbalancer/net/aa02d38c1ce264a5691a0bbfcbe64f37/a595692994f7ec8d' cannot be deleted because it is currently associated with another service status code: 400, request id: 57fc2ecd-4d82-4f4c-ad63-4eaf81fdc331
Slack thread: https://redhat-internal.slack.com/archives/C04EUL1DRHC/p1678964549274709
Reference:
hosted cluster 22ad0p03svv24fgfvi14alf4cv4c8jn2 on MC hs-mc-vdritd53g
HC version 4.12.4, hypershift version 42e85b6ed107c4b99a5ef00b886e1943ea896095