Sphoorti, 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' notification. Note that the logic to send the update.start notification: https://github.com/openstack/neutron/blob/master/neutron/api/v2/base.py#L453 occurs *before* the request body is prepared: https://github.com/openstack/neutron/blob/master/neutron/api/v2/base.py#L458 which ultimately calls into logic to add the tenant ID: https://github.com/openstack/neutron/blob/master/neutron/api/v2/base.py#L500 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. Thanks, Eoghan ----- 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 >