yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  DNSDomain.register_for_zone races

Status in OpenStack Compute (nova):
  Expired

Bug description:
  2 simultaneous calls to DNSDomain.register_for_zone or
  DNSDomain.register_for_project will race. The winner is undefined.
  Consequently, the caller has no way of knowing if the DNSDomain is
  appropriately registered following a call. register_for_zone or
  register_for_project will not currently generate an error in this
  case.

  I can think of 2 ways to resolve this:

  1. Assert that only an unregistered domain can be registered.
  Attempting to register a registered domain is an error. This would be
  a semantic change to the existing APIs.

  2. Create new APIs which additionally take the expected current
  registration, and fail if it is not as expected. Deprecate the
  existing APIs.

  I favour the former.

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