q-svc.log if filled with [networking_odl.journal.journal] printouts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-odl |
Opinion
|
Low
|
Unassigned | ||
Bug Description
After loading devstack with ODL networking V2 (ODL version – beryllium),
The q-svc.log log file in folder [/opt/stack/logs] is filled with printouts as follows:
2016-07-18 17:00:34.898 26079 DEBUG networking_
2016-07-18 17:00:34.899 25990 DEBUG networking_
2016-07-18 17:00:34.899 25990 DEBUG networking_
in networking ODL V1 those printouts do not appear at all.
I logged the bug since I think we should have better log messages that will appear in "info" level so that we can have a deployed system without "debug" level messages.
| Changed in networking-odl: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| Arvind Somya (asomya) wrote | #1 |
| Changed in networking-odl: | |
| status: | Confirmed → Won't Fix |
| status: | Won't Fix → Opinion |
I'm not sure what the bug is here. The V2 driver is completely different from the V1 driver, the V1 driver doesn't use a journalling mechanism. These messages should not appear at all when run at INFO level logging.
If you don't want to see debug messages then simply turn off debug in your config. We do have other messages relevant to journaling but not as verbose that appear at INFO level logging.