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

Bug 1559116

Summary:	OS::Aodh::EventAlarm resource does not exist in RHOSP 10
Product:	Red Hat OpenStack	Reporter:	nalmond
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Ronnie Rasouli <rrasouli>
Severity:	low	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	amcleod, apannu, jose.lema, mburns, nalmond, pkilambi, ramishra, rhel-osp-director-maint, sbaker, shardy, srevivo, therve, zbitter
Target Milestone:	z9	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-heat-7.0.6-3.el7ost	Doc Type:	Enhancement
Doc Text:	With this enhancement, the OS::Aodh::EventAlarm Heat resource type is now included in RHEL-OSP 10. This enhancement provides a Heat interface to allow users to define alarms that can be evaluated based on events that other OpenStack services emit. For example; service update, create, or delete events.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-17 16:57:52 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 nalmond 2018-03-21 17:44:06 UTC

Description of problem:
Ocata introduced a heat resource to define aodh event alarms https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Aodh::EventAlarm

This was added upstream with this commit:
https://review.openstack.org/#/c/381057/

Can this be backported to RHOSP 10?

Version-Release number of selected component (if applicable):


How reproducible:
Always in RHOSP 10

Steps to Reproduce:
1. Deploy RHOSP 10
2. Attempt to use OS::Aodh::EventAlarm in a heat template

Actual results:
Resource does not exist

Expected results:
Resource exists

Additional info:
https://bugs.launchpad.net/heat/+bug/1628695

Comment 1 Rabi Mishra 2018-03-22 09:57:06 UTC

We don't backport resource plugins upstream. However, if there is a compelling business reason to do so downstream only, we can consider it.

Comment 4 Zane Bitter 2018-03-27 15:33:26 UTC

No objection to this from a technical perspective. The new resource type landed relatively early in Ocata development, so nothing it depends on had been modified between Newton and Ocata.

Comment 19 Alex McLeod 2018-09-03 08:04:20 UTC

Hi there,

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field.

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Thanks,
Alex

Comment 23 errata-xmlrpc 2018-09-17 16:57:52 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-2018:2716