ovs logs are trashed with healthcheck messages from ovslib
Bug #1687064 reported by
Ihar Hrachyshka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Low
|
Unassigned | ||
| ovsdbapp |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Those messages are all over the place:
2017-04-28 14:34:06.478 16259 DEBUG ovsdbapp.
We should probably suppress them, they don't seem to carry any value. If there is value in knowing when something stopped working, maybe consider erroring in this failure mode instead of logging in happy path.
| Changed in neutron: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| tags: | added: ovs usability |
Revision history for this message
| Terry Wilson (otherwiseguy) wrote | #1 |
| tags: | added: logging |
Revision history for this message
| Terry Wilson (otherwiseguy) wrote | #2 |
| Changed in neutron: | |
| status: | Confirmed → Fix Released |
| Changed in ovsdbapp: | |
| status: | New → Invalid |
To post a comment you must log in.
We should not suppress them, they do have value. They are DEBUG logs and they are DEBUG information useful for finding race conditions. We specifically go to work to enable these logs--suppressing them would just be never setting them up in the first place with the vlog monkeypatching.
I agree with making them more targeted during testing, though.