yahoo-eng-team team mailing list archive

[David Stanek <dstanek@xxxxxxxxxxx>]

I think this is something that should be fixed in oslo if it needs to be
fixed at all. There are a several different ways to configure logging
and they don't play nicely together: There is log-file (and or log-dir),
use_strerr and our logging.conf. There may be others that I don't know
about.

** Also affects: oslo
   Importance: Undecided
       Status: New

** Changed in: keystone
       Status: In Progress => Invalid

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

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

Status in OpenStack Identity (Keystone):
  Invalid
Status in Oslo - a Library of Common OpenStack Code:
  New

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