yahoo-eng-team team mailing list archive

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

The bp serias "generic resource pools" [1] should solve this (very old)
issue.

References:
[1] https://github.com/openstack/nova-specs/blob/63db6163968f9e25c4b6cb121c21660092bd4d88/specs/newton/approved/generic-resource-pools.rst

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

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

Title:
  Boot volumes API race

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  When there is a race for a volume between 2 or more instances, it is
  possible for more than one to pass the API check. All of them will get
  scheduled as a result, and only one will actually successfully attach
  the volume, while others will go to ERROR.

  This is not ideal since we can reserve the volume in the API, thus
  making it a bit more user friendly when there is a race (the user will
  be informed immediately instead of seeing an errored instance).

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