yahoo-eng-team team mailing list archive

[OpenStack Infra <2102095@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/944101
Committed: https://opendev.org/openstack/neutron/commit/979385d8f992093dc7e0b31631ba9adb89e42e90
Submitter: "Zuul (22348)"
Branch:    master

commit 979385d8f992093dc7e0b31631ba9adb89e42e90
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Wed Mar 12 10:22:38 2025 +0000

    [OVN][Placement] Reduce log level to error when Placement exception
    
    Closes-Bug: #2102095
    Change-Id: I2eb7c1bc7f6e0e04aead13330513aa2da3cc89ab


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2102095

Title:
  [OVN][Placement] Change the message level when a Placement exception
  happens

Status in neutron:
  Fix Released

Bug description:
  The current log level when a Placement API call error happens is
  excessive [1]. An exception should be thrown when a sever issue,
  mostly related with the code, happens during the execution.

  If a Placement API returns an exception, this should be logged as an
  error. The error shows what the problem is without returning a stack
  traceback, that is not necessary and could be seen as a Neutron API
  code error.

  Example of the Neutron API log with the same Placement API exception,
  with different log levels: [2]

  [1]https://github.com/openstack/neutron/blob/2f6640d6dc886314b11b0dd53eb203f27f874047/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/extensions/placement.py#L101
  [2]https://paste.opendev.org/show/bUsWsLp8rjDczn2FzU5m/

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