Reviewed: https://review.opendev.org/c/openstack/neutron/+/880982 Committed: https://opendev.org/openstack/neutron/commit/c3602ac19b62b77d3cb763746e124881d4c061e4 Submitter: "Zuul (22348)" Branch: master
commit c3602ac19b62b77d3cb763746e124881d4c061e4 Author: Elvira García <[email protected]> Date: Thu Apr 20 16:39:12 2023 +0200 [OVN] Update ovn meter when neutron server reloads Up until now, we needed to remove all logging objects to see the meter-band properties being changed after a server restart. Now we check for inconsistencies between the neutron configuration and the OVN meter-band object after a restart. The function create_ovn_fair_meter is now located in the ovn_driver instead of the log_driver so as to be able to call it from the maintenance task. Closes-bug: #2017145 Signed-off-by: Elvira García <[email protected]> Change-Id: I24cef85ed68c893a740445707f88296d763c8de8 ** 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/2017145 Title: [OVN] - Logging configuration doesn't change after neutron restart Status in neutron: Fix Released Bug description: Right now adding a new rate and burst limit to the network_log configuration in the ml2_conf.ini file won't make any effect on the system as OVN meter-band will remain unchanged. To make it work you need to remove every logging object (so that the meter entry in OVN is removed) and then recreate them again. This is not how it should work. 100% reproducible Steps: - Add log plugin - Add log object to the project - change rate and burst limit - restart the neutron server to see if changes applied To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2017145/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
