-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14, 4.15, 4.16
-
Informational
-
No
-
Rejected
-
False
-
Description of problem:
The ingress operator provides the "SyncLoadBalancerFailed" status with a message that says "The kube-controller-manager logs may contain more details.". Depending on the platform, that isn't accurate as we are transitioning the CCM out-of-tree to the "cloud-controller-manager". Code Link: https://github.com/openshift/cluster-ingress-operator/blob/55780444031714fc931d90af298a4b193888977a/pkg/operator/controller/ingress/status.go#L874
- AWS has been out-of-tree since 4.14:
OCPCLOUD-1404 - Azure has been out-of-tree since 4.14:
OCPCLOUD-1128 - GCP has been out-of-tree since 4.15:
OCPCLOUD-1756
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Steps to Reproduce:
1. Create a IngressController with a broken LoadBalancer-type service so it produces "SyncLoadBalancerFailed" (TBD, I'll try to figure out how to produce this...)
2.
3.
Actual results:
"The kube-controller-manager logs may contain more details."
Expected results:
"The cloud-controller-manager logs may contain more details."
Additional info:
