yahoo-eng-team team mailing list archive

[OpenStack Infra <1962574@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/nova/+/827467
Committed: https://opendev.org/openstack/nova/commit/646fc51732b60b46385ceff0c7ea2c23372bbd72
Submitter: "Zuul (22348)"
Branch:    master

commit 646fc51732b60b46385ceff0c7ea2c23372bbd72
Author: Fabian Wiesel <fabian.wiesel@xxxxxxx>
Date:   Wed Feb 2 10:13:06 2022 +0100

    Transport context to all threads
    
    The nova.utils.spawn and spawn_n methods transport
    the context (and profiling information) to the
    newly created threads. But the same isn't done
    when submitting work to thread-pools in the
    ComputeManager.
    
    The code doing that for spawn and spawn_n
    is extracted to a new function
    and called to submit the work to the thread-pools.
    
    Closes-Bug: #1962574
    Change-Id: I9085deaa8cf0b167d87db68e4afc4a463c00569c


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  Live-Migration does not log consistently

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===========
  Most log entries contain the request-id and user-context (user-id, project-id, etc...), but not the live-migration in a thread-pool

  Expected result
  ===============
  For example, I would expect for example the live-migration to be logged the following way:

  2022-03-01 12:29:21,245 7 INFO nova.compute.manager
  [req-399ed405-efde-4197-8fe2-8b7f7a7cca0c <user-id> <project-id> -
  <user-domain> <project-domain>] live_migration data is ....

  Actual result
  =============
  Instead various log messages are containing a "[-]" indicating that the request-context is not set in the thread.

  2022-03-01 12:29:21,245 7 INFO nova.compute.manager [-] live_migration
  data is ....

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

  All versions are affected. Including master branch.

  2. Which hypervisor did you use?
     N/A

  2. Which storage type did you use?
     N/A

  3. Which networking type did you use?
     N/A

  Logs & Configs
  ==============

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