yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69142
[Bug 1732000] [NEW] nova-api does not log config options when run in wsgi mode
Public bug reported:
The ServiceLauncher/ProcessLauncher code in oslo.services will check a
'log_options' option on start of the service/process and if True (the
default) it will log the config option values.
The nova-api service used to run with eventlet only via oslo.service,
but since Pike we can run nova-api using wsgi (uwsgi, mod_wsgi, etc).
However, the wsgi app doesn't log the config options.
Compare to this ocata nova-api log:
http://logs.openstack.org/59/509659/1/check/legacy-tempest-dsvm-neutron-
full/d84ca9f/logs/screen-n-api.txt.gz
To master (queens):
http://logs.openstack.org/04/514904/20/check/legacy-tempest-dsvm-
neutron-full/0cd3ce7/logs/screen-n-api.txt.gz
The placement-api wsgi app does log the options, but uses different
logic (it doesn't honor the log_options option):
http://logs.openstack.org/04/514904/20/check/legacy-tempest-dsvm-
neutron-full/0cd3ce7/logs/screen-placement-
api.txt.gz#_Nov_10_06_47_27_532714
https://github.com/openstack/nova/blob/16.0.0/nova/api/openstack/placement/wsgi.py#L59
So there are two things to fix here:
1. nova-api should log config options on startup when running under
wsgi.
2. placement-api should check the log_options option rather than the
debug option.
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Affects: nova/pike
Importance: Undecided
Status: New
** Tags: api placement
** Also affects: nova/pike
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1732000
Title:
nova-api does not log config options when run in wsgi mode
Status in OpenStack Compute (nova):
Triaged
Status in OpenStack Compute (nova) pike series:
New
Bug description:
The ServiceLauncher/ProcessLauncher code in oslo.services will check a
'log_options' option on start of the service/process and if True (the
default) it will log the config option values.
The nova-api service used to run with eventlet only via oslo.service,
but since Pike we can run nova-api using wsgi (uwsgi, mod_wsgi, etc).
However, the wsgi app doesn't log the config options.
Compare to this ocata nova-api log:
http://logs.openstack.org/59/509659/1/check/legacy-tempest-dsvm-
neutron-full/d84ca9f/logs/screen-n-api.txt.gz
To master (queens):
http://logs.openstack.org/04/514904/20/check/legacy-tempest-dsvm-
neutron-full/0cd3ce7/logs/screen-n-api.txt.gz
The placement-api wsgi app does log the options, but uses different
logic (it doesn't honor the log_options option):
http://logs.openstack.org/04/514904/20/check/legacy-tempest-dsvm-
neutron-full/0cd3ce7/logs/screen-placement-
api.txt.gz#_Nov_10_06_47_27_532714
https://github.com/openstack/nova/blob/16.0.0/nova/api/openstack/placement/wsgi.py#L59
So there are two things to fix here:
1. nova-api should log config options on startup when running under
wsgi.
2. placement-api should check the log_options option rather than the
debug option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1732000/+subscriptions
Follow ups