[openstack-dev] [neutron][ceilometer] Network Notification plugin broken. Ceilometer bug #1243292

Eoghan Glynn eglynn at redhat.com
Sat Nov 2 17:17:12 UTC 2013


Just copying the list with some pointers on this issue that
I gave you on IRC.

Running 'neutron router-update' show that the tenant ID is absent
from the 'router.update.start' but present in the 'router.update.end'

Note that the logic to send the update.start notification:


occurs *before* the request body is prepared:  


which ultimately calls into logic to add the tenant ID:


which is then available when the update.end notification
is finally sent.

You'll need to investigate if this neutron code-path can be
restructured so as to ensure that the tenant ID is always set a
priori, in advance of the first notification from this workflow.

Neutron folks - please chime in if I've misread that code.


----- Original Message -----
> Team,
> The tenant_id, subnet, network are missing from some of the network
> notification payloads, and this looks like it happened rather recently.
> The ceilometer expects them to be present on each of the notifications.
> Is this Neutron's expected behavior? Would changing the dictionary reference
> from [key] to .get(key, default_value) help?
> Here is the link to the bug
> https://bugs.launchpad.net/ceilometer/+bug/1243292
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list