yahoo-eng-team team mailing list archive

[Yair Fried <yfried@xxxxxxxxxx>]

Public bug reported:

Associating Floating IP with neutron takes too long to show up in VM's
details ('nova show' or 'compute_client.servers.get()') and even longer
when there's more than 1 VM involved.

when launching 2 VMs with floating IP you can see in the log that it passes once:
"unchecked floating IPs: {}"
and fails
"Timed out while waiting for the floating IP assignments to propagate"

http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/0541dff/console.html
http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/f383f4b/console.html
http://logs.openstack.org/01/55101/31/check/check-tempest-dsvm-neutron/321413a/console.html
http://logs.openstack.org/97/62697/5/check/check-tempest-dsvm-neutron/960c6ad/console.html

also - the floating ip is accessible long time before it is updated in
nova DB

How to reproduce:
https://review.openstack.org/#/c/62697/

So the problem is both:
1. the time it takes for nova to get the update
and
2. the timeout defined in the tempest neutron-gate

since I don't see this in my local setup (rhos-4.0), I don't know if
this is due to stress in neutron or nova, or if it's a devstack issue

** Affects: devstack
     Importance: Undecided
         Status: New

** Affects: neutron
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: tempest
     Importance: Undecided
         Status: New


** Tags: network

** Attachment added: "Jenkins log files"
   https://bugs.launchpad.net/bugs/1262529/+attachment/3932409/+files/logs.tar.gz

** Also affects: tempest
   Importance: Undecided
       Status: New

** Also affects: neutron
   Importance: Undecided
       Status: New

** Also affects: devstack
   Importance: Undecided
       Status: New

** Summary changed:

- Floating IP takes too long to update in nova and even longer
+ Floating IP takes too long to update in nova and even longer for multiple VMs

** Description changed:

  Associating Floating IP with neutron takes too long to show up in VM's
  details ('nova show' or 'compute_client.servers.get()') and even longer
- when there's more than 1 VM involvede.
+ when there's more than 1 VM involved.
  
- you can see in the log that it passes once:
+ when launching 2 VMs with floating IP you can see in the log that it passes once:
  "unchecked floating IPs: {}"
- and fails 
+ and fails
  "Timed out while waiting for the floating IP assignments to propagate"
  
  http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/0541dff/console.html
  http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/f383f4b/console.html
  http://logs.openstack.org/01/55101/31/check/check-tempest-dsvm-neutron/321413a/console.html
  http://logs.openstack.org/97/62697/5/check/check-tempest-dsvm-neutron/960c6ad/console.html
  
  also - the floating ip is accessible long time before it is updated in
  nova DB
  
  How to reproduce:
  https://review.openstack.org/#/c/62697/
  
- So the problem is both the time it takes for nova to get the update, and
- the timeout in defined in the neutron-gate
+ So the problem is both:
+ 1. the time it takes for nova to get the update
+ and
+ 2. the timeout defined in the tempest neutron-gate
+ 
+ since I don't see this in my local setup (rhos-4.0), I don't know if
+ this is due to stress in neutron or nova, or if it's a devstack issue

-- 
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/1262529

Title:
  Floating IP takes too long to update in nova and even longer for
  multiple VMs

Status in devstack - openstack dev environments:
  New
Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  New

Bug description:
  Associating Floating IP with neutron takes too long to show up in VM's
  details ('nova show' or 'compute_client.servers.get()') and even
  longer when there's more than 1 VM involved.

  when launching 2 VMs with floating IP you can see in the log that it passes once:
  "unchecked floating IPs: {}"
  and fails
  "Timed out while waiting for the floating IP assignments to propagate"

  http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/0541dff/console.html
  http://logs.openstack.org/01/55101/28/check/check-tempest-dsvm-neutron/f383f4b/console.html
  http://logs.openstack.org/01/55101/31/check/check-tempest-dsvm-neutron/321413a/console.html
  http://logs.openstack.org/97/62697/5/check/check-tempest-dsvm-neutron/960c6ad/console.html

  also - the floating ip is accessible long time before it is updated in
  nova DB

  How to reproduce:
  https://review.openstack.org/#/c/62697/

  So the problem is both:
  1. the time it takes for nova to get the update
  and
  2. the timeout defined in the tempest neutron-gate

  since I don't see this in my local setup (rhos-4.0), I don't know if
  this is due to stress in neutron or nova, or if it's a devstack issue

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