yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Also affects: nova/ocata
   Importance: Undecided
       Status: New

** Changed in: nova/ocata
       Status: New => Confirmed

** Also affects: nova/newton
   Importance: Undecided
       Status: New

** Changed in: nova/newton
       Status: New => Confirmed

** Changed in: nova/newton
   Importance: Undecided => Medium

** Changed in: nova/ocata
   Importance: Undecided => Medium

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

Title:
  addFloatingIP conflict is tracing in n-api logs

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  Confirmed
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  This Tempest negative test was added back in March:

  https://github.com/openstack/tempest/commit/343ca198166ded0bbf6e23535aeae0ea15a922dc

  It passes but it results in an ugly stacktrace in the n-api logs:

  http://logs.openstack.org/89/466889/2/gate/gate-tempest-dsvm-neutron-
  full-ubuntu-
  xenial/57732b0/logs/screen-n-api.txt.gz?level=TRACE#_May_24_07_30_30_975142

  Which is normally a place where we shouldn't stacktrace if it's not a
  500 error.

  This is an expected situation, and we should be able to handle the 409
  Conflict from Neutron and translate that to a proper error handled at
  the top REST API controller.

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