yahoo-eng-team team mailing list archive

[Sebastian Lohff <2129681@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When creating a VPNaaS endpoint group with duplicate endpoints, the API
request hangs for >= 3 minutes and then fails. I would expect endpoints
in a group to be unique and therefore an API request in this regard to
fail immediately with an error message instead of hanging.

Looking at the VPNaaS DB models we can see that the endpoint table has
all of its keys marked as primary, which also marks them as unique. This
means, when Neutron tries to insert duplicate endpoints into this table,
we get a DBError, which is then retried (I think due to the POST /
create call having a retry decorator by default). With a maximum of 20
retries and max 10s per retry this presents more as a hanging API call
to the user. Instead I would expect an immediate error message from the
API, telling the user about the duplicate endpoint.

** Affects: neutron
     Importance: Undecided
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2129681

Title:
  VPNaaS endpoint group creating with non-unique endpoints takes a long
  time to fail

Status in neutron:
  In Progress

Bug description:
  When creating a VPNaaS endpoint group with duplicate endpoints, the
  API request hangs for >= 3 minutes and then fails. I would expect
  endpoints in a group to be unique and therefore an API request in this
  regard to fail immediately with an error message instead of hanging.

  Looking at the VPNaaS DB models we can see that the endpoint table has
  all of its keys marked as primary, which also marks them as unique.
  This means, when Neutron tries to insert duplicate endpoints into this
  table, we get a DBError, which is then retried (I think due to the
  POST / create call having a retry decorator by default). With a
  maximum of 20 retries and max 10s per retry this presents more as a
  hanging API call to the user. Instead I would expect an immediate
  error message from the API, telling the user about the duplicate
  endpoint.

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