← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1312504] [NEW] wrong message format reported by ceilometer log

 

Public bug reported:

Here's the error log reported by ceilometer:

2014-04-24 18:06:37.316 15522 INFO ceilometer.network.notifications [-]
network notification {u'event_type': u'floatingip.update.end',
'billing': 0, u'real_host': u'controller_1', u'timestamp': u'2014-04-24
10:06:36.053392', u'message_id': u'a5f8ee68-e0e4-4b1f-a1cb-
90bf95c3bb20', u'priority': u'INFO', '_id':
ObjectId('5358e22d29d6303ca2194940'), u'publisher_id':
u'network.controller_1', u'payload': {u'floatingip': {u'router_id':
u'fdd1f3f8-da38-48d0-94d1-65dc51123bfc', u'status': u'DOWN',
u'tenant_id': u'6ac23f29f125473995d2eed507f3a012',
u'floating_network_id': u'e8c3f1e5-3b63-4b1f-8e6a-29412819e7f2',
u'fixed_ip_address': u'10.25.0.248', u'floating_ip_address':
u'192.168.242.187', u'port_id': u'9c16d8ec-b991-40ce-81a0-10ad947c2c3a',
u'id': u'39c4db2c-bcd8-414b-9012-fe098dc6b65e'}}}

2014-04-24 18:06:37.317 15522 ERROR stevedore.extension [-] error calling 'floatingip': 'id'
2014-04-24 18:06:37.317 15522 ERROR stevedore.extension [-] 'id'
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension Traceback (most recent call last):
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/stevedore/extension.py", line 247, in _invoke_one_plugin
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     response_callback(func(e, *args, **kwds))
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/ceilometer/notification.py", line 165, in _process_notification_for_ext
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     p(list(ext.obj.to_samples(notification)))
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/ceilometer/network/notifications.py", line 85, in process_notification
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     LOG.error('Just print id %s',message['payload']['id'])
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension KeyError: 'id'
2014-04-24 18:06:37.317 15522 TRACE stevedore.extension

When I associated a floating ip with a vm, "floatingip.update.start"
message can be processed in the right way but "floating.update.end"
message cannot be properly processed.

I figured out that for the two messages sent by neutron, the resource
part of the payload is not the same. "floatingip.update.start" has the
"id" in the resource part, but "floatingip.update.end" doesn't have it.
It is because the "id" is lost in the payload generation.

** Affects: neutron
     Importance: Undecided
     Assignee: Li Ma (nick-ma-z)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Li Ma (nick-ma-z)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1312504

Title:
  wrong message format reported by ceilometer log

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Here's the error log reported by ceilometer:

  2014-04-24 18:06:37.316 15522 INFO ceilometer.network.notifications
  [-] network notification {u'event_type': u'floatingip.update.end',
  'billing': 0, u'real_host': u'controller_1', u'timestamp':
  u'2014-04-24 10:06:36.053392', u'message_id': u'a5f8ee68-e0e4-4b1f-
  a1cb-90bf95c3bb20', u'priority': u'INFO', '_id':
  ObjectId('5358e22d29d6303ca2194940'), u'publisher_id':
  u'network.controller_1', u'payload': {u'floatingip': {u'router_id':
  u'fdd1f3f8-da38-48d0-94d1-65dc51123bfc', u'status': u'DOWN',
  u'tenant_id': u'6ac23f29f125473995d2eed507f3a012',
  u'floating_network_id': u'e8c3f1e5-3b63-4b1f-8e6a-29412819e7f2',
  u'fixed_ip_address': u'10.25.0.248', u'floating_ip_address':
  u'192.168.242.187', u'port_id': u'9c16d8ec-b991-40ce-
  81a0-10ad947c2c3a', u'id': u'39c4db2c-bcd8-414b-9012-fe098dc6b65e'}}}

  2014-04-24 18:06:37.317 15522 ERROR stevedore.extension [-] error calling 'floatingip': 'id'
  2014-04-24 18:06:37.317 15522 ERROR stevedore.extension [-] 'id'
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension Traceback (most recent call last):
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/stevedore/extension.py", line 247, in _invoke_one_plugin
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     response_callback(func(e, *args, **kwds))
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/ceilometer/notification.py", line 165, in _process_notification_for_ext
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     p(list(ext.obj.to_samples(notification)))
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension   File "/usr/lib/python2.6/site-packages/ceilometer/network/notifications.py", line 85, in process_notification
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension     LOG.error('Just print id %s',message['payload']['id'])
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension KeyError: 'id'
  2014-04-24 18:06:37.317 15522 TRACE stevedore.extension

  When I associated a floating ip with a vm, "floatingip.update.start"
  message can be processed in the right way but "floating.update.end"
  message cannot be properly processed.

  I figured out that for the two messages sent by neutron, the resource
  part of the payload is not the same. "floatingip.update.start" has the
  "id" in the resource part, but "floatingip.update.end" doesn't have
  it. It is because the "id" is lost in the payload generation.

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


Follow ups

References