Maintenance task doesn't have enough logging verbosity
Bug #1837003 reported by
Daniel Alvarez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Medium
|
Lucas Alvares Gomes |
Bug Description
When the maintenance task kicks in and fixes some inconsistencies, it's hard to tell through the logs. Plus it doesn't have enough verbosity in the logs to tell which objects have been fixed.
Right now, when debugging this issue, I've been grepping for "Maintenance task synchronization finished" and scrolling back on the logs to figure out via ovsdbapp traces what have been fixed.
It'd be nice if we could add a summary of the problems detected at [0]. This will also help figuring out how likely race conditions occur and which objects are more prone to those under load.
Changed in networking-ovn: | |
importance: | Undecided → Medium |
assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/671442
Review: https:/