Description of problem:
Hi,
My customer has the following issue:
Two services of type LoadBalancer were created in our cluster that remained in Pending state and no Octavia LoadBalancers were created in Openstack. We couldn't find any relevant errors in the Openshift logging and in Openstack there weren't any issues with Octavia either. We increased the log level of the kubecontrollermanagers.operator.openshift.io, which restarted the kube-controller-manager pods in the openshift-kube-controller-manager namespace. After the restart, the LoadBalancers were created in Octavia.
Version-Release number of selected component (if applicable):
OCP 4.6.15
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
We'd expect the LoadBalancers to be created in the reconcile loop of the kube-controller-managers without needing to restart them.
We'd also expect the events in the namespace in which the LoadBalancer service is created to show more logs/error messages when creating them through the cloud provider fails.
Additional info: