Associate FIP: ports appearing when already assigned floating IPs

[Steve McLellan]

Repro (in stock devstack):
1) Create an instance on a private network
2) Create and associate a floating IP
3) Create and try to associate a second IP

The second time will cause an error "Error: The requested instance port is already associated with another floating IP."

Note that the instance's port is listed both times, though it's not possible to attach two FIPs to the same fixed IP. It looks like there is some filtering code in api/neutron.py but it may not be doing the right thing.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/151410

[OpenStack Infra (hudson-openstack)]

Change abandoned by David Lyle (<email address hidden>) on branch: master
Review: https://review.openstack.org/151410
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.