Some log levels not correctly setup from flags (e.g. nova.utils)

Bug #712814 reported by justinsb
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Unassigned

Bug Description

Some loggers are created before the flags are read, so are not set to DEBUG even when running with the --verbose flag set.

I added a logging.warn statement to log._get_level_from_flags to see/verify this, and these loggers are created before the FLAG variables are dumped (which I presume is immediately after they are set): nova.root, nova.exception, sqlalchemy, nova.utils. amqplib, nova.fakerabbit, nova.rpc.

This is for the compute node (I haven't checked if other daemons exhibit the same problem or if they have a different set of flags)

Running against trunk.

WARNING:root:LOG nova.root => INFO
2011-02-03 17:16:03,818 WARNING nova.root [-] LOG nova.exception => INFO
2011-02-03 17:16:03,873 WARNING nova.root [-] LOG sqlalchemy => WARN
2011-02-03 17:16:03,913 WARNING nova.root [-] LOG nova.utils => INFO
2011-02-03 17:16:04,006 WARNING nova.root [-] LOG amqplib => WARN
2011-02-03 17:16:04,056 WARNING nova.root [-] LOG nova.fakerabbit => INFO
2011-02-03 17:16:04,057 WARNING nova.root [-] LOG nova.rpc => INFO

2011-02-03 17:16:04,096 AUDIT nova.root [-] Starting compute node (version 2011.1-LOCALBRANCH:LOCALREVISION)
2011-02-03 17:16:04,096 DEBUG nova.root [-] Serving nova-compute from MainProcess (pid=29867) serve /home/justinsb/lefthand/nova/nova/nova/service.py:224
2011-02-03 17:16:04,097 DEBUG nova.root [-] Full set of FLAGS: from MainProcess (pid=29867) serve /home/justinsb/lefthand/nova/nova/nova/service.py:225
2011-02-03 17:16:04,097 DEBUG nova.root [-] rabbit_retry_interval : 10 from MainProcess (pid=29867) serve /home/justinsb/lefthand/nova/nova/nova/service.py:228
...<snip>...
2011-02-03 17:16:04,101 DEBUG nova.root [-] verbose : True from MainProcess (pid=29867) serve /home/justinsb/lefthand/nova/nova/nova/service.py:228

Related branches

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Ken Pepple (ken-pepple) wrote :

i think the fix for 718360 takes care of some of these problems ...

Thierry Carrez (ttx)
Changed in nova:
status: Confirmed → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.2
status: Fix Committed → Fix Released
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.