Dashboard doesn't list floating IP associated with VM instance

[Aniket Kulkarni]

I upgraded my existing setup from folsom to grizzly. Then I was able to successfully associate floating IP to VM instances form dashboard. But dashboard then doesn't list associated floating IP. It is very difficult for user to remember what floating IP is associated with each instance (as our quota per user is really large, it is impossible to remember unless you note down somewhere).

So for time being, till this is fixed, pl atleast suggest some workaround as our user base for this setup is high so impact here is also high.

[Gabriel Hurley (gabriel-hurley)]

Horizon displays the data provided by Nova's API, so I strongly suspect this may be a problem with what Nova is returning. Can you enable debug logging for the client (or use python-novaclient directly) to do a server list command and provide the returned data?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Akihiro Motoki (amotoki)]

I guess the original reporter uses Neutron.
When neutron is used, an operation of associating floating IP to an instance is an API call to Neutron.
Nova seems to sync network related information with neutron (quantum) periodically.

I confirmed floating IP associated is not listed in the instance table just after associating an floating IP, but after waiting for around 30 minutes I saw both fixed IP and floating IP are displayed. (Grizzly and Havana have the same behavior.)

It is ideal to display associated floating IP just after associate operation, but it is an acceptable limitation.
In addition, the problem the author pointed is "it is impossible to remember unless you note down somewhere" and we can see floating IP addresses in the instance table and detail page if we wait after less than one minute.
(Note that we can see floating IP is associated in Floating IP table in "Access and Securtiy" even just after association because information is retrieved from Neutron.)

[Akihiro Motoki (amotoki)]

If we improve the issue reported, it should be fixed in nova not horizon, though I think it is still acceptable.
I will mark this bug as "Won't fix".