yahoo-eng-team team mailing list archive

[Gorka Eguileor <1922052@xxxxxxxxxxxxxxxxxx>]

Moving bug to os-brick since that's where we are going to fix it,
although the issue was caused by a change in Nova's code and it will
only be visible on Nova.

** Project changed: nova => os-brick

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

Title:
  Missing os-brick commands in debug mode

Status in os-brick:
  Triaged
Status in oslo.privsep:
  Fix Released

Bug description:
  To debug os-brick's attach and detach code developers and system
  administrators rely on seeing  what commands are actually being
  executed by os-brick.

  The os-brick library relies on the DEBUG logs from the libraries (such
  as ``oslo_concurrency.processutils``) for this purpose instead of
  duplicating log entries by logging the calls and stdout-stderr itself.

  The default configuration in Nova no longer logs those os-brick
  commands when running on debug mode.

  This issue was introduced when fixing bug #1784062, as the fix was to
  set ALL privsep calls to log only INFO level messages.

  The current solution is to set the ``default_log_levels``
  configuration option in nova and include
  ``oslo.privsep.daemon=DEBUG`` in it.

  The default for os-brick should be the other way around, it should
  allow emitting DEBUG messages on debug mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/os-brick/+bug/1922052/+subscriptions