There is a potential bug in lbaas_v2 implementation related to attaching a floating IP to a loadbalancer. The current implementation looks up port ID based on the loadbalancer's IP address because port ID was not available from gophercloud library. This can cause a problem if the configured openstack user manages one or more networks with overlapping subnets. The IP address of the loadbalancer would not be unique in this case and the returned port id can be invalid.
This bug can be addressed once Gophercloud PR 20 is merged. This change exposes a loadbalancer's port ID from lbaas v2.
dagnello
commented
8 years ago
There is a potential bug in lbaas_v2 implementation related to attaching a floating IP to a loadbalancer. The current implementation looks up port ID based on the loadbalancer's IP address because port ID was not available from gophercloud library. This can cause a problem if the configured openstack user manages one or more networks with overlapping subnets. The IP address of the loadbalancer would not be unique in this case and the returned port id can be invalid.
This bug can be addressed once Gophercloud PR 20 is merged. This change exposes a loadbalancer's port ID from lbaas v2.