Comment 0 for bug 1631825

Using Mitaka 3.1.0.0-25. Floating IP assignment works functionally as expected. However after making the FIP assignment to a VM in Projects and the assignment is confirmed, the IP address is not shown in Horizon. In fact the drop-down continues to show “Associate” but not “Disassociate”, so it is not possible to disassociate the FIP from the Project page in Horizon. However from the Instances page in Admin as well as under Access/Security/FIP, I do see the FIP assignment and able to disassociate the FIP from the VM.

Rahul Sharma investigated this problem and made the following observations:

There are two issues here:
1. Network info for instances in nova didn't sync from neutron.
I could see the floating ip info for instances in nova refresh-network for each of the instances.

2. Few new checks have been added to horizon code in mitaka. Code for floating ip parsing expects a format that is bit different than the addresses format returned in nova list/show output (vn is prepended and we get a list inside a dict instead of list). I'll verify these outputs with vanilla neutron/nova.

In case its a horizon bug, we'll generate a new package with patch.

I see some part of this horizon fip parsing code on similar lines in latest kilo/liberty too.