OpenShift LoadBalancer subnet-id has been modified in OpenStack cloudprovider configuration, but still the old subnet-id is in use
Issue
-
In the process of moving the OpenStack provided LoadBalancer network to a different one (i.e. new separate VLAN), the creation of the OpenShift LoadBalancer fails with
Type Reason Age From Message ---- ------ ---- ---- ------- Normal EnsuringLoadBalancer 14s (x3 over 30s) service-controller Ensuring load balancer Warning CreatingLoadBalancerFailed 13s (x3 over 30s) service-controller Error creating load balancer (will retry): failed to ensure load balancer for service external-ip/egress-2: error creating loadbalancer a90736272104c11eaa457fa163ea6dd8: error creating loadbalancer {a90736272104c11eaa457fa163ea6dd8 Kubernetes external service a90736272104c11eaa457fa163ea6dd8 2c8f634b-a212-46ae-9399-3aac3270fe9b <nil> }: Expected HTTP response code [201 202] when accessing [POST http://openstack.example.com:9696/v2.0/lbaas/loadbalancers], but got 409 instead {"NeutronError": {"message": "Quota exceeded for resources: ['loadbalancer'].", "type": "OverQuota", "detail": ""}}
Environment
- Red Hat OpenShift Container Platform (OCP) 3.9, 3.10, 3.11
- Red Hat OpenStack Platform (OSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.