yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #66394
[Bug 1696668] Re: ovo_rpc semantics "warnings" are too verbose
Reviewed: https://review.openstack.org/482000
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5b78a81e2d152f2854b22c25cd7cc47eaff2859b
Submitter: Jenkins
Branch: master
commit 5b78a81e2d152f2854b22c25cd7cc47eaff2859b
Author: YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>
Date: Mon Jul 10 14:11:24 2017 +0900
ovo_rpc: Avoid flooding logs with semantic violation warning
Still log them, but not repeatedly.
Also, lower the level from error to warning.
The message has been there long enough. (since [1])
Relevant parties should have already known if their service
plugin needs to be refactored or not. It's no longer
desirable to keep the warning that loud.
[1] I5efc625c5e8565693e795d70e0f85810552d38cd
Closes-Bug: #1696668
Change-Id: I4f1f399ac8e1c9acec9c7bce2f57c053c98e3031
** 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/1696668
Title:
ovo_rpc semantics "warnings" are too verbose
Status in neutron:
Fix Released
Bug description:
It logs traceback at ERROR level.
I know it's intentional, but given that it isn't a real issue for some configurations,
it's too verbose and potentially hides other issues by spamming logs too much.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696668/+subscriptions
References