yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

I disagree that we should move these out of DEBUG. I actually think we
probably need to put more of these down in DEBUG unless there are lost
messages, and we should info or warn on those.

** Changed in: nova
       Status: New => Opinion

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

Title:
  network-vif-plugged events should be Info on nova compute

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  Version
  =======
  IceHouse on rhel

  Description
  ===========

  In order to track network-vif-plugged events across openetsack :
  Nova-API send  event network-vif-plugged under AUDIT level ,

  " AUDIT nova.api.openstack.compute.contrib.server_external_events
  [req-7bd8ca07-a133-4b57-a6e3-a4340115475d
  ca48398ab5f244e3bdfb798f94920fd1 d7e1cf5e67804ef0b8e27329a38105ef]
  Creating event network-vif-plugged"

  Neutron server shos

  "INFO neutron.notifiers.nova [-] Nova event response: {u'status': u'completed', u'tag': u'd883de4f-9c05-4f49-9125-316708d36d4d', u'name': u'network-vif-plugged', u'server_uuid': u'fea1a088-212a-4e08-baa5-f745d9bf2cca', u'code': 200}
  "

  BUT nova compute shows  "event network-vif-plugged" only on DEBUG, 
  IMHO it should be Info/Audit level as well so we can track that NOVA-API created event to neutron and compute processed that event  

  Current  level on compute :
  "DEBUG nova.compute.manager [req-7bd8ca07-a133-4b57-a6e3-a4340115475d ca48398ab5f244e3bdfb798f94920fd1 d7e1cf5e67804ef0b8e27329a38105ef] [instance: fea1a088-212a-4e08-baa5-f745d9bf2cca] Processing event network-vif-plugged-d883de4f-9c05-4f49-9125-316708d36d4d _process_instance_event /usr/lib/python2.7/site-packages/nova/compute/manager.py:5665"

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