cleanup debug logs to make them as 'operator-safe' as possible

Bug #1673249 reported by Kevin Benton on 2017-03-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

According to [1], it has become operator procedure to run Neutron with debug enabled and so having bad debug logs is bad PR for Neutron. In addition to the referenced patch, we should probably go through and cleanup debug log statements that could be misleading to operators.


Changed in neutron:
importance: Undecided → Low
tags: added: low-hanging-fruit
Changed in neutron:
status: New → Confirmed
Changed in neutron:
assignee: nobody → Ihar Hrachyshka (ihar-hrachyshka)
status: Confirmed → In Progress

Submitter: Jenkins
Branch: master

commit 4f7fc8435f9340aae293bdcfef99201956ec2838
Author: Ihar Hrachyshka <email address hidden>
Date: Wed Mar 8 04:05:18 2017 +0000

    Stop spilling tracebacks during normal operation

    Yes, they are innocent; yes, we log them with DEBUG level. But they
    scare people, they make people judge the software, they are bad PR, and
    they are probably redundant, string representation of the exception
    should be enough. If there is an issue that will result in retry
    attempts used without remedy, only then we should spill tracebacks and
    scare users.


    Partial-Bug: #1673249
    Change-Id: I791a52161635da64b1840c01ee6cf56a51bc7400

Changed in neutron:
assignee: Ihar Hrachyshka (ihar-hrachyshka) → nobody
Changed in neutron:
assignee: nobody → Prashant Sanjay Sarvi (prashantsarvi)
Changed in neutron:
assignee: Prashant Sanjay Sarvi (prashantsarvi) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers