Comment 9 for bug 1529062

The issue is in Nova or, more likely, Neutron.
I checked how this works for the single fixed IPs network and single instance's interface:
- nova add-fixed-ip replaces the instance's fixed IP to the new one. Shouldn't it add the IP to the interface instead?
- the 2nd floating ip associated with the new fixed IP works, while the old floating IP stops working (because there is no old fixed IP - it was replaced).
- if manually added to the interface, the original fixed IP association works again and both floating IPs are OK.

And this doesn't work if the new fixed IP is from another network and belongs to another attached interface.