Changing log level in the configuration file has no effect

Bug #1644002 reported by Kristi Nikolla
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mix and Match (mixmatch)
Invalid
Undecided
Unassigned

Bug Description

Even though the logging level is set to DEBUG in the configuration file, things logged with debug level don't appear.

We may not be setting the logging level correctly, so it defaults to INFO instead.

Revision history for this message
Kristi Nikolla (knikolla) wrote :

Log level needs to be set as defined per the oslo.log options rather than the python logger options.

Therefore to set the level to DEBUG, you need to change [DEFAULT]/debug to True.

Changed in mixmatch:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.