Log statement improperly output in nova-manage
Bug #1018431 reported by
Jay Pipes
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Davanum Srinivas (DIMS) | ||
Folsom |
Fix Released
|
Low
|
Nikola Đipanov |
Bug Description
Not sure if it's worth fixing, since we're not focusing on nova-manage, but thought I'd log it anyway as a low-hanging fruit:
http://
Looks like the SQLlchemy log handler isn't being set up correctly.
tags: | added: nova-manage |
Changed in nova: | |
assignee: | unicell (unicell) → nobody |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Well, it is not a bug actually, but due to the debug level setting.
The log message occurs when nova-manage trying to retrieve network information, via DB api layer, which in turn lazy-loaded SQLAlchemy database backend. And it honors the global logging level.
According to default devstack setting, FLAGS.verbose is set in nova.conf, which set the global DEBUG logging level.
Please try to comment out "verbose=True" in nova.conf, and you'll not see this log statement again.