auto_assigned_floating_ip - tools taking long time to bring back floating IP assigned
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned |
Bug Description
ii nova-api 2012.1~rc1-0ubuntu2 OpenStack Compute - API frontend
ii nova-cert 2012.1~rc1-0ubuntu2 OpenStack Compute - certificate management
ii nova-common 2012.1~rc1-0ubuntu2 OpenStack Compute - common files
ii nova-compute 2012.1~rc1-0ubuntu2 OpenStack Compute - compute node
ii nova-compute-kvm 2012.1~rc1-0ubuntu2 OpenStack Compute - compute node (KVM)
ii nova-network 2012.1~rc1-0ubuntu2 OpenStack Compute - Network manager
ii nova-objectstore 2012.1~rc1-0ubuntu2 OpenStack Compute - object store
ii nova-scheduler 2012.1~rc1-0ubuntu2 OpenStack Compute - virtual machine scheduler
ii python-nova 2012.1~rc1-0ubuntu2 OpenStack Compute Python libraries
ii python-novaclient 2012.1~rc1-0ubuntu1 client library for OpenStack Compute API
in /etc/nova/nova.conf
--auto_
and I fire up an instance.
Everything works, a private IP is assigned... the instance is running... but it can take an inordinate amount of time (anywhere upwards of 2 mins, sometimes a lot longer ~10 mins) to associate a floating IP automatically.
On further investigation it appears the floating IP gets assigned almost immediately, the database table (nova.floating_ips) is updated - and I can use the floating IP to log in - but 'nova list' and 'Horizon' don't receive this information until a good few minutes wait.
The upshot is that instances are ready almost immediately, but to the end user they're not until they see the floating IP assigned.
The instance_info_cache needs to be updated after ip assignment. What's happening is the ip is assigned, but since all of compute/api use the instance_info_cache to get at network data, it won't show up until a get_instance_ nw_info is called by compute (usually during the cache heal task).