yahoo-eng-team team mailing list archive

[Albert White <albert.white@xxxxxxxxx>]

Public bug reported:


Using Solaris 11.3 with Juno (0.2014.2.2)

When I associate a floating-ip address using Horizon, the ip does not
appear in nova show or nova list until after I have issued a 'nova
refresh-network' on the instance (or until I do a 'nova reboot').

However 'nova floating-ip-list' does correctly show the floating ip as
associated, as does horizon and 'neutron floatingip-list'

If I make the association using 'nova floating-ip-associate' no refresh-
network is required.


The same issue arises with disassociating a floating-ip. 

The issue appears to be that 'nova list/show' read from the
nova.instance_info_caches table and when the floating ip is associated
via horizon that cache is not updated.

Either associating a floating ip in horizon should update this cache, or
nova list/show should update it before displaying information.

Specifically to reproduce:
1. Create an instance either via command line or horizon, verify with nova list:
| 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112                 
2. Associate a floating IP via horizon
3. run 'nova list' or 'nova show' - the floating ip address will not be listed.
4. 'nova floating-ip-list' will show the floating ip proving that 'nova list' is presenting out of date information
nova list:
| 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112                 || 129.156.230.17  | 54c45d69-eacd-4add-a717-dc925d876053 | 10.10.10.112 | external_network |

5. 'nova refresh-network' will force the cache to be updated and nova list will only then show the correct information.
nova refresh-network 54c45d69-eacd-4add-a717-dc925d876053
| 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112, 129.156.230.17 |

This is an inconsistency between how floating ips are associated and
also with the information nova itself knows about an instance (show
versus  floating-ip-list reporting different things). I would expect
nova list to show the floating-ip without the need for refresh-network
or a reboot since nova floating-ip-list etc. can display the correct
information.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: solaris

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1515727

Title:
  nova list/show does not show floatingip information updated from
  horizon

Status in OpenStack Compute (nova):
  New

Bug description:
  
  Using Solaris 11.3 with Juno (0.2014.2.2)

  When I associate a floating-ip address using Horizon, the ip does not
  appear in nova show or nova list until after I have issued a 'nova
  refresh-network' on the instance (or until I do a 'nova reboot').

  However 'nova floating-ip-list' does correctly show the floating ip as
  associated, as does horizon and 'neutron floatingip-list'

  If I make the association using 'nova floating-ip-associate' no
  refresh-network is required.

  
  The same issue arises with disassociating a floating-ip. 

  The issue appears to be that 'nova list/show' read from the
  nova.instance_info_caches table and when the floating ip is associated
  via horizon that cache is not updated.

  Either associating a floating ip in horizon should update this cache,
  or nova list/show should update it before displaying information.

  Specifically to reproduce:
  1. Create an instance either via command line or horizon, verify with nova list:
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112                 
  2. Associate a floating IP via horizon
  3. run 'nova list' or 'nova show' - the floating ip address will not be listed.
  4. 'nova floating-ip-list' will show the floating ip proving that 'nova list' is presenting out of date information
  nova list:
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112                 || 129.156.230.17  | 54c45d69-eacd-4add-a717-dc925d876053 | 10.10.10.112 | external_network |

  5. 'nova refresh-network' will force the cache to be updated and nova list will only then show the correct information.
  nova refresh-network 54c45d69-eacd-4add-a717-dc925d876053
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1                      | ACTIVE | -          | Running     | internal_network=10.10.10.112, 129.156.230.17 |

  This is an inconsistency between how floating ips are associated and
  also with the information nova itself knows about an instance (show
  versus  floating-ip-list reporting different things). I would expect
  nova list to show the floating-ip without the need for refresh-network
  or a reboot since nova floating-ip-list etc. can display the correct
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1515727/+subscriptions