Bug 1221924

Summary: event_definitions.yaml is missing
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: openstack-ceilometerAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: jruzicka, pbrady, yeylon
Target Milestone: gaKeywords: Triaged
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-ceilometer-2015.1.0-6.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:24:19 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 Yurii Prokulevych 2015-05-15 09:24:02 UTC 
Description of problem:

File 'event_definitions.yaml' is used to drive the conversion from notifications to events.
Without it an empty set of definitions is assumed.

Expected results:

event_definitions.yaml is part of ceilometer package 
(similar to event_pipeline.yaml or pipeline.yaml)


Packages versions:
openstack-ceilometer-notification-2015.1.0-2.el7ost.noarch
openstack-ceilometer-common-2015.1.0-2.el7ost.noarch
python-ceilometerclient-1.0.13-1.el7ost.noarch
openstack-ceilometer-alarm-2015.1.0-2.el7ost.noarch
python-ceilometer-2015.1.0-2.el7ost.noarch
openstack-ceilometer-collector-2015.1.0-2.el7ost.noarch
openstack-ceilometer-central-2015.1.0-2.el7ost.noarch
openstack-ceilometer-api-2015.1.0-2.el7ost.noarch
openstack-ceilometer-compute-2015.1.0-2.el7ost.noarch
Comment 3 Pradeep Kilambi 2015-06-25 19:19:33 UTC 
I pushed a fix for this upstream in rdo: 

https://review.gerrithub.io/#/c/237634/
Comment 7 Yurii Prokulevych 2015-07-03 10:27:29 UTC 
rpm -qf /etc/ceilometer/event_definitions.yaml 
openstack-ceilometer-notification-2015.1.0-6.el7ost.noarch
Comment 9 errata-xmlrpc 2015-08-05 13:24:19 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-2015:1548