default oslo_messaging log level bumped to INFO in pike
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Medium
|
Edward Hope-Morley | ||
OpenStack Nova Compute Charm |
Fix Released
|
Medium
|
Edward Hope-Morley |
Bug Description
I'm debugging a nova rpc issue on Pike and have noticed that the default log level for the oslo_messaging modules have increased to INFO from DEBUG (in default_log_levels) meaning that I no longer see logs like:
2018-10-11 11:54:10.426 1382 DEBUG oslo_messaging.
These log levels are set using the default_log_levels config opt in [DEFAULT] so setting the following allows these logs to return (annoyingly you need to set everything to be able to change any one):
default_log_levels = amqp=WARN,
We need to be able to manipulate this via the charms when DEBUG is enabled since it is essential for debugging.
Changed in charm-nova-cloud-controller: | |
milestone: | none → 19.04 |
Changed in charm-nova-compute: | |
milestone: | none → 19.04 |
Changed in charm-nova-cloud-controller: | |
importance: | Undecided → Medium |
Changed in charm-nova-compute: | |
importance: | Undecided → Medium |
tags: | added: sts |
Changed in charm-nova-cloud-controller: | |
status: | New → Triaged |
Changed in charm-nova-compute: | |
status: | New → Triaged |
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Edward Hope-Morley (hopem) |
Changed in charm-nova-compute: | |
assignee: | nobody → Edward Hope-Morley (hopem) |
Changed in charm-nova-compute: | |
status: | Fix Committed → Fix Released |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
btw the reason for this is that oslo.log stable/ocata does not include oslo_messaging in its DEFAULT_LOG_LEVELS [1] whereas pike does.
[1] https:/ /github. com/openstack/ oslo.log/ blob/stable/ ocata/oslo_ log/_options. py#L21