Bug 1458053

Summary:	Neutron doesn't send notifications to Ceilometer since OSP11
Product:	Red Hat OpenStack	Reporter:	Ihar Hrachyshka <ihrachys>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED ERRATA	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	amuller, aschultz, chrisw, ihrachys, nyechiel, oblaut, pkilambi, srevivo
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-10.0.1-5.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-19 17:03:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ihar Hrachyshka 2017-06-01 21:46:48 UTC

Description of problem: notifications are supposed to be enabled by default (via neutron-dist.conf), but due to the fact that in Ocata we dropped old aliases for notification drivers, and we used such an old alias in neutron-dist.conf, it stopped working.

This totally breaks billing for Neutron services.


Steps to Reproduce:
1. set up default OSP11 environment with Ceilometer.
2. create neutron resources.

Actual results: events for new resources not seen in Ceilometer.


Expected results: events should be available via Ceilometer.

Comment 1 Alan Pevec 2017-06-03 00:58:04 UTC

> Description of problem: notifications are supposed to be enabled by default
> (via neutron-dist.conf), but due to the fact that in Ocata we dropped old
> aliases for notification drivers, and we used such an old alias in
> neutron-dist.conf, it stopped working.
> 
> This totally breaks billing for Neutron services.

@pradk I would argue that deployment tools should explicitly set notification options when Telemetry is enabled, and not rely on defaults.

Comment 2 Ihar Hrachyshka 2017-06-03 20:01:17 UTC

Alan, I agree, but there should be an explicit decision (and installer integration) for that in place. + release note and stuff. We can't do it without thinking through the implications like we did for Ocata.

There is a noop driver for what I know that could be explicitly picked if we don't need to do anything. (Or maybe empty list which is the default is enough?)

Let's discuss it in broader scope than just for Neutron.

Comment 4 Alex Schultz 2017-07-03 22:24:53 UTC

Just to add a comment here, this probably shouldn't be fixed in packaging as it does require some knowledge of the end user's deployment to know if ceilometer is actually configured. If the notifications are enabled and no one is listening, this can fill up the rabbit queues for the operator. It would be better to disable it by default in packaging (unless there's some other functionality that requires it) and enable it only if ceilometer is being deployed.

Comment 5 Ihar Hrachyshka 2017-07-03 23:10:56 UTC

@Alex, feel free to report a bug against neutron, and we will have a proper look at it (with handling upgrades and whatnot).

Comment 6 Alexander Stafeyev 2017-07-16 17:06:06 UTC

Hi, 
Is network create is enough to trigger ceilometer event ? 

tnx

Comment 7 Ihar Hrachyshka 2017-07-17 14:23:56 UTC

Yes.

Comment 12 errata-xmlrpc 2017-07-19 17:03:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1785