← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1230360] Re: keystone-all --log-file logs to stdout

 

The default for use_stderr was changed to False.

** Changed in: oslo.log
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1230360

Title:
  keystone-all --log-file logs to stdout

Status in OpenStack Identity (keystone):
  Invalid
Status in oslo.log:
  Fix Released

Bug description:
  The help text for keystone-all says if I set --log-file then logging
  goes to the output file, otherwise it goes to stdout. But logging goes
  to stdout whether I set --log-file or not.

  Here's the output without --log-file:

  $ tools/with_venv.sh bin/keystone-all
  2013-09-25 10:35:40.229 3406 INFO keystone.common.environment [-] Environment configured as: eventlet
  2013-09-25 10:35:40.652 3406 WARNING keystone.token.provider [-] keystone.conf [signing] token_format is deprecated in favor of keystone.conf [token] provider
  2013-09-25 10:35:40.747 3406 INFO keystone.common.environment.eventlet_server [-] Starting bin/keystone-all on 0.0.0.0:35357
  2013-09-25 10:35:40.751 3406 INFO keystone.common.environment.eventlet_server [-] Starting bin/keystone-all on 0.0.0.0:5000

  Here's the output with --log-file:

  $ tools/with_venv.sh bin/keystone-all --log-file /tmp/keystone-log1.txt
  2013-09-25 10:35:54.747 3425 INFO keystone.common.environment [-] Environment configured as: eventlet
  2013-09-25 10:35:55.168 3425 WARNING keystone.token.provider [-] keystone.conf [signing] token_format is deprecated in favor of keystone.conf [token] provider
  2013-09-25 10:35:55.262 3425 INFO keystone.common.environment.eventlet_server [-] Starting bin/keystone-all on 0.0.0.0:35357
  2013-09-25 10:35:55.266 3425 INFO keystone.common.environment.eventlet_server [-] Starting bin/keystone-all on 0.0.0.0:5000

  I expected that when I used --log-file that there would be no ouput to
  stdout.

  Note that it wrote the same thing to the log file so maybe this is
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1230360/+subscriptions