yahoo-eng-team team mailing list archive

[Joe Gordon <1399788@xxxxxxxxxxxxxxxxxx>]

Note this is the gate devstack setup.

This is  neutron.conf http://logs.openstack.org/80/139880/3/check/check-
tempest-dsvm-neutron-full/1fee100/logs/etc/neutron/neutron.conf.txt.gz

so we are using the default logging_context_format_string which looks to
be:


%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s

from

http://logs.openstack.org/80/139880/3/check/check-tempest-dsvm-neutron-
full/1fee100/logs/screen-q-svc.txt.gz#_2014-12-08_14_22_29_990

It looks like the important difference is

[%(request_id)s %(user_name)s %(project_id)s%(color)s]
vs.
 [%(request_id)s %(user_identity)s]

** Changed in: neutron
       Status: Invalid => New

** Changed in: neutron
     Assignee: venkata anil (anil-venkata) => (unassigned)

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

Title:
  neutron doesn't log tenant_id and user_id along side req-id in logs

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  neutron logs:  [req-94a39f87-e470-4032-82af-9a6b429b60fa None]
  while nova logs: [req-c0b4dfb9-8af3-40eb-b0dd-7b576cfd1d55 AggregatesAdminTestJSON-917687995 AggregatesAdminTestJSON-394398414]

  
  Nova uses the format: #logging_context_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s

  Without knowing the user and tenant its hard to understand what the
  logs are doing when multiple tenants are using the cloud.

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