ovo_rpc semantics "warnings" are too verbose

Bug #1696668 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Low
YAMAMOTO Takashi

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.

tags: added: midokura-jira-tracked
Revision history for this message
Trevor McCasland (twm2016) wrote :

This can easily be seen as a bug if they aren't verbose enough.. I'm confused on how a log can be hidden. I can see how it can be hard to find but it's still there.

Changed in neutron:
status: New → Incomplete
status: Incomplete → Opinion
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

Trevor,

i'm not sure what you mean.
do you mean it's fine to make other logs hard to find?
it makes trouble shooting harder.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/482000

Changed in neutron:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: Opinion → In Progress
Changed in neutron:
importance: Undecided → Low
milestone: none → pike-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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 <email address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0rc1

This issue was fixed in the openstack/neutron 11.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers