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

Bug 1233871

Summary:	Updating alarm's property with the same value produces empty record in alarm-history output's
Product:	Red Hat OpenStack	Reporter:	Yurii Prokulevych <yprokule>
Component:	openstack-ceilometer	Assignee:	Mehdi ABAAKOUK <mabaakou>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yurii Prokulevych <yprokule>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	eglynn, jruzicka, mabaakou, srevivo
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ceilometer-2015.1.3-3.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-07 05:31:48 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-06-19 15:57:49 UTC

Description of problem:
When alarm's property is updated with the same value than empty record is added to the alarm-history output.
Detailed log in the upstream bug

Version-Release number of selected component (if applicable):
2015.1.0-2.el7ost.noarch

Comment 5 Chris Dent 2015-06-25 13:55:18 UTC

Yurii we'd like to fix this for A1 but whether that happens or not depends to some degree on whether the upstream fix is ready on master to then be backported to kilo and then in a position where we can push it into the RPM.

So yes, A1 is the goal, but the upstream bug is currently being worked on by a non-red-hatter, so there's ambiguity in the timetable over which we have no control.

Comment 6 Chris Dent 2015-07-20 14:04:56 UTC

Added the backport to upstream kilo gerrit.