yahoo-eng-team team mailing list archive

[Hua Wang <wanghua.humble@xxxxxxxxx>]

Public bug reported:

nova keeps the RequestConext in threading.local, so it can print the
request_id in the logs. But when booting an instance, it spawns a new
greenthread to build the instance. The RequestContext is not kept in the
threading.local of the new greenthread, so we can not print the
request_id in the logs.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  nova keeps the RequestConext in threading.local, so it can print the
  request_id in the logs. But when booting an instance, it spawns a new
  greenthread to build the instance. The RequestContext is not kept in the
- threading.local of the new greenthread, so we cann't print the
+ threading.local of the new greenthread, so we can not print the
  request_id in the logs.

-- 
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/1442174

Title:
  can not print request_id in some logs when booting an instance

Status in OpenStack Compute (Nova):
  New

Bug description:
  nova keeps the RequestConext in threading.local, so it can print the
  request_id in the logs. But when booting an instance, it spawns a new
  greenthread to build the instance. The RequestContext is not kept in
  the threading.local of the new greenthread, so we can not print the
  request_id in the logs.

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