Incorrect floating IP shown when multiple networks used

[Corey O'Brien]

When multiple private networks are used, the fixed_ip for a floating ip may match a device on each network. Currently, if a floating ip has a fixed ip that matches the vip for a load balancer, the dashboard incorrectly assumes that the floating ip is associated with the load balancer.

https://github.com/openstack/neutron-lbaas-dashboard/blob/06ed719/neutron_lbaas_dashboard/api/rest/lbaasv2.py#L387-L399

Consider two networks using 10.0.0.0/24. On network 1 there is a nova server assigned the IP 10.0.0.2 with a floating ip associated. On network 2 there is a loadbalancer assigned the IP 10.0.0.2 with no floating ip associated. The dashboard will show the loadbalancer associated to the floating ip.

The reliable way to determine if a floating ip is associated with a load balancer is to match the port ids.