OpenStack project with multiple networks/subnets. Multiple servers exist in each subnet, and they have the same (internal) IP address in their respective subnet.
After creating a service of type LoadBalancer, the OpenStack load balancer might be configured with the wrong subnet and not see it's members.
The LB remains in "operating_status": "ERROR",. The vip_subnet_id field is a subnet of a different network.
What you expected to happen:
A working LB.
How to reproduce it:
Create multiple networks/subnets. Multiple servers exist in each subnet, and some have the same (internal) IP address in their respective subnet.
Create a loadbalancer in one of the subnets. Check the loadbalancer for the vip_subnet_id field.
Anything else we need to know?:
Environment:
openstack-cloud-controller-manager(or other related binary) version: 1.30.0
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Prerequisite:
OpenStack project with multiple networks/subnets. Multiple servers exist in each subnet, and they have the same (internal) IP address in their respective subnet.
After creating a service of type
LoadBalancer, the OpenStack load balancer might be configured with the wrong subnet and not see it's members.The LB remains in
"operating_status": "ERROR",. Thevip_subnet_idfield is a subnet of a different network.What you expected to happen:
A working LB.
How to reproduce it:
Create multiple networks/subnets. Multiple servers exist in each subnet, and some have the same (internal) IP address in their respective subnet.
Create a loadbalancer in one of the subnets. Check the loadbalancer for the
vip_subnet_idfield.Anything else we need to know?:
Environment: