[Openstack-operators] floating ip autoassign vs instance_info_caches (possible bug)

Linux Datacenter linuxdatacenter at gmail.com
Fri Jan 27 10:38:03 UTC 2012


Hi,

I am using nova with the latest trunk here:

dpkg -l |grep nova
ii  nova-api
2012.1~e4~20120126.12306-0ubuntu0ppa1~oneiric1 OpenStack Compute - API
frontend
ii  nova-common
2012.1~e4~20120126.12306-0ubuntu0ppa1~oneiric1 OpenStack Compute - common
files
ii  nova-scheduler
2012.1~e4~20120126.12306-0ubuntu0ppa1~oneiric1 OpenStack Compute - virtual
machine scheduler
ii  python-nova
2012.1~e4~20120126.12306-0ubuntu0ppa1~oneiric1 OpenStack Compute Python
libraries
ii  python-novaclient
2012.1~e3~20120125.472-0ubuntu0ppa1~oneiric1   client library for OpenStack
Compute API


I turned on the feature --auto_assign_floating_ip.

What I see is that even though the floating ip is assigned correctly to an
instance, it does not appear instantly in "euca-describe-instances" and
"nova list" output.

The reason probably is that there's no entry for the floating ip in
instance_info_caches table. However, you can see the address is allocated
in floating_ips table.

My guess is that the floating ip autoassign code does not update the
instance_info_caches table correctly.

Cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120127/382fa364/attachment-0002.html>


More information about the Openstack-operators mailing list