yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Given we are after RC1 (which means that we only accept regression
bugfixes for RC2 and later versions), I think we should just document
the current caveat in https://docs.openstack.org/api-guide/compute
/accelerator-support.html and trying to backport the bugfix for a later
Ussuri release (say 21.0.1).


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

** Changed in: nova/ussuri
   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/1874664

Title:
  Boot more than one instances failed with accelerators in its flavor

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) ussuri series:
  New

Bug description:
  When boot more than one instance with accelerator, and the
  accelerators are in one compute node, there will be two problems as
  below:

  One problem is as we always get the first item(alloc_reqs[0]) in
  alloc_reqs, when we iterator the second instance, it will throw
  conflict exception when putting the allocations.

  Another is as we always get the first item in
  alloc_reqs_by_rp_uuid.get(selected_host.uuid), the selected_alloc_req
  is always stable, that will cause the values in selections_to_return
  are same . In fact, it's not right for subsequent operations.

  More details you can see:
  https://etherpad.opendev.org/p/filter_scheduler_issue_with_accelerators

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