yahoo-eng-team team mailing list archive

[Ryan Moats <rmoats@xxxxxxxxxx>]

Public bug reported:

Version of Nova/OpenStack: liberty

Calls to associate a floating IP with an instance currently returns a
202 status.  When proxying these calls to neutron, just returning 202
without having validated the status of the floating IP first leads to
raceful failures in tempest scenario tests (for example, see the
test_volume_boot_pattern failure in
http://logs.openstack.org/20/225420/1/check/gate-tempest-dsvm-neutron-
dvr/a78a052/logs/testr_results.html.gz)

Is it possible to (when proxying to neutron) first verify the status of
the neutron floating IP before returning the 202 status

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova API proxy to neutron should avoid race-ful behavior

Status in OpenStack Compute (nova):
  New

Bug description:
  Version of Nova/OpenStack: liberty

  Calls to associate a floating IP with an instance currently returns a
  202 status.  When proxying these calls to neutron, just returning 202
  without having validated the status of the floating IP first leads to
  raceful failures in tempest scenario tests (for example, see the
  test_volume_boot_pattern failure in
  http://logs.openstack.org/20/225420/1/check/gate-tempest-dsvm-neutron-
  dvr/a78a052/logs/testr_results.html.gz)

  Is it possible to (when proxying to neutron) first verify the status
  of the neutron floating IP before returning the 202 status

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