Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1436599

Summary:	event_dispatchers=panko is missing in ceilometer.conf when panko is installed i n deployment
Product:	Red Hat OpenStack	Reporter:	Sasha Smolyak <ssmolyak>
Component:	openstack-tripleo-heat-templates	Assignee:	Pradeep Kilambi <pkilambi>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	jdanjou, jschluet, mburns, pkilambi, rhel-osp-director-maint, slinaber, ssmolyak
Target Milestone:	beta	Keywords:	Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	instack-undercloud-6.0.0-5.el7ost openstack-tripleo-heat-templates-6.0.0-4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 20:15:09 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 Sasha Smolyak 2017-03-28 09:37:00 UTC

Description of problem:
Line 
event_dispatchers=panko 
is missing in ceilometer.conf when deploying with panko enabled (passing the panko.yaml)

Version-Release number of selected component (if applicable):
openstack-panko-common-2.0.1-1.el7ost.noarch
openstack-panko-api-2.0.1-1.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP11 overcloud with Panko enabled (-e environments/services/panko.yaml)
2. Open ceilometer.conf

Actual results:
no line
event_dispatchers=panko 

Expected results:
There's supposed to be line 
event_dispatchers=panko 


Additional info:

Comment 4 Jon Schlueter 2017-04-03 17:20:12 UTC

on THT upstream/stable/ocata and instack-undercloud upstream/stable/ocata

Comment 6 Sasha Smolyak 2017-04-20 10:49:00 UTC

Checked both in undercloud and overcloud

Comment 7 errata-xmlrpc 2017-05-17 20:15:09 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/RHEA-2017:1245