yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:


nova master as of 20170831

The _set_allocations method used to write allocations to the placement
API will raise a 400 when a resource class results in a NotFound
exception. We want that 400. The problem is that the message associated
with the error users the resource provider uuid from whatever resource
provider was the last one in a loop, not the one that creates the error.
See:

https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/allocation.py#L231-L234

and the loop prior.

This is not a huge deal because it's unlikely that people are inspecting
error responses all that much, but it would be nice to fix.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement

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

Title:
  When setting an allocation with multiple resource providers and one of
  them does not exist the error message can be wrong

Status in OpenStack Compute (nova):
  New

Bug description:
  
  nova master as of 20170831

  The _set_allocations method used to write allocations to the placement
  API will raise a 400 when a resource class results in a NotFound
  exception. We want that 400. The problem is that the message
  associated with the error users the resource provider uuid from
  whatever resource provider was the last one in a loop, not the one
  that creates the error. See:

  https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/allocation.py#L231-L234

  and the loop prior.

  This is not a huge deal because it's unlikely that people are
  inspecting error responses all that much, but it would be nice to fix.

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