-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.12
-
?
-
Critical
-
None
-
ShiftStack Sprint 226
-
1
-
Rejected
-
False
-
-
None
Description of problem:
When creating a LB type svc with the default cloud provider configuration, it creates an internal LB without a FIP, showing the next message: W1004 10:54:52.530354 1 loadbalancer.go:1145] Floating network configuration not provided for Service lb-test-ns/lb-test-svc, forcing to ensure an internal load balancer service There is no LoadBalancer section in the cloud-provider config so the external network ID should be discovered.
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-09-28-204419
How reproducible:
Always
Steps to Reproduce (find here lb-test-manifests.yaml
):
1. Create a LB type svc $ oc create -f lb-test-manifests.yaml 2. Check LB and FIP creation
Actual results:
LB is created but the FIP is not being created
Expected results:
FIP creation and assignment
Additional info:
$ oc -n lb-test-ns describe svc lb-test-svc Name: lb-test-svc Namespace: lb-test-ns Labels: app=lb-test-dep Annotations: loadbalancer.openstack.org/load-balancer-id: 7af45577-9352-4382-837a-0c45f984e333 Selector: app=lb-test-dep Type: LoadBalancer IP Family Policy: SingleStack IP Families: IPv4 IP: 172.30.214.87 IPs: 172.30.214.87 LoadBalancer Ingress: 10.196.3.148 Port: <unset> 80/TCP TargetPort: 8080/TCP NodePort: <unset> 30889/TCP Endpoints: 10.129.2.10:8080,10.131.0.19:8080 Session Affinity: None External Traffic Policy: Cluster Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning SyncLoadBalancerFailed 169m service-controller Error syncing load balancer: failed to ensure load balancer: load balancer 7af45577-9352-4382-837a-0c45f984e333 is not ACTIVE, current provisioning status: PENDING_CREATE Normal EnsuringLoadBalancer 169m (x3 over 170m) service-controller Ensuring load balancer Normal EnsuredLoadBalancer 169m (x2 over 169m) service-controller Ensured load balancer