yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

As of master 2016-12-12, there are four LOG.warning calls in
nova.objects.resource_provider, all associated in some way with
inventory capacity being violated in some fashion. Two of these log and
then raise an exception, two are simply warnings.

For the two that log and then raise, instead of logging in the objects
it would be more correct to raise where the exception is caught (the
placement api layer).

** 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/1649384

Title:
  in placement service capacity exceeded LOG.warning call is in wrong
  place

Status in OpenStack Compute (nova):
  New

Bug description:
  As of master 2016-12-12, there are four LOG.warning calls in
  nova.objects.resource_provider, all associated in some way with
  inventory capacity being violated in some fashion. Two of these log
  and then raise an exception, two are simply warnings.

  For the two that log and then raise, instead of logging in the objects
  it would be more correct to raise where the exception is caught (the
  placement api layer).

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