yahoo-eng-team team mailing list archive

[David Ripton <dripton@xxxxxxxxxx>]

Two core Nova reviewers thought this was too much noise in the logs.  So
admins will need to set the loglevel to DEBUG to see this info.

** Changed in: nova
       Status: In Progress => Won't Fix

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

Title:
  Network changes should be logged as INFO not DEBUG

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  nova/network/linux_net.py and nova/virt/libvirt/vif.py call various
  brctl and 'ip addr' commands to create and destroy network bridges, IP
  addresses, network devices, and network routes.   These are
  significant changes that can render the node completely unusable if
  they're wrong, and it would be nice to indicate that we're doing so to
  give admins a starting point for debugging.  Currently we log these
  operations at DEBUG level, which means they are not logged unless
  someone changes the default_notification_level in nova.conf.  We
  should log them at INFO instead.

  None of these operations should be called frequently enough to create
  excessive log output.

  Downstream bug report
  https://bugzilla.redhat.com/show_bug.cgi?id=903504

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