Delayed display of floating IPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Rajat Sharma |
Bug Description
Using nova 1:2014.1.4-0ubuntu2 (Icehouse) on Ubuntu 14.04.2 LTS
After associating a floating IP address to an instance in Build/Spawning state, 'nova list' and 'nova show' need - per default - a lot of time (up to 40 minutes) to display that floating IP.
Steps to reproduce:
* Launching instance via Horizon
* Associate a floating IP address while instance is in Build/Spawning state via Horizon
Expected result:
* 'nova list' and 'nova show' should print the floating IP consistently
* the floating IP should be part of the related row in nova.instance_
Actual result:
* while in Build/Spawning state 'nova list' and 'nova show' displays the floating IP address
* while in Build/Spawning state the floating IP is part of the related row in nova.instance_
* when the instance is switching to Active/Running state, the floating IP disappears in 'nova list', 'nova show' and the nova.instance_
* a little later (related to heal_instance_
Side note 1: This issue does not occur, if the floating IP is associated after launching (in Active/Running state).
Side note 2: In Horizon, the floating IP is listed all the time.
Side note 3: The floating IP is working (ping, ssh), even if not displayed.
Output of 'select * from nova.instance_
Instance in Build/Spawning:
*******
created_at: 2015-04-24 09:06:23
updated_at: 2015-04-24 09:06:43
deleted_at: NULL
id: 1671
network_info: [{"ovs_
instance_uuid: f0d22419-
deleted: 0
Instance switches to Active/Running ("floating_ips" becomes empty):
*******
created_at: 2015-04-24 09:06:23
updated_at: 2015-04-24 09:07:04
deleted_at: NULL
id: 1671
network_info: [{"ovs_
instance_uuid: f0d22419-
deleted: 0
After ~ 40 minutes:
*******
created_at: 2015-04-24 09:06:23
updated_at: 2015-04-24 09:45:35
deleted_at: NULL
id: 1671
network_info: [{"ovs_
instance_uuid: f0d22419-
deleted: 0
The related part in nova-compute.log
2015-04-24 11:07:04.544 14860 INFO nova.virt.
[...]
2015-04-24 11:45:36.012 14860 DEBUG nova.compute.
Current workaround:
Setting 'heal_instance_
Maybe it could be possible to fire up the 'instance _heal_instance_
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: low-hanging-fruit network |
Changed in nova: | |
assignee: | nobody → Naga Praveen (nilla) |
Changed in nova: | |
assignee: | Naga Praveen (nilla) → nobody |
Changed in nova: | |
assignee: | nobody → Yashpal (ybcopenstack) |
Changed in nova: | |
assignee: | Yashpal (ybcopenstack) → Rajat Sharma (coolrajatsharma03) |
Changed in nova: | |
status: | Confirmed → Fix Released |
description: | updated |
Bug not reproducible on "master" branch