Bug 1233871 - Updating alarm's property with the same value produces empty record in alarm-history output's
Summary: Updating alarm's property with the same value produces empty record in alarm-...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ceilometer
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 7.0 (Kilo)
Assignee: Mehdi ABAAKOUK
QA Contact: Yurii Prokulevych
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-19 15:57 UTC by Yurii Prokulevych
Modified: 2017-01-07 05:31 UTC (History)
4 users (show)

Fixed In Version: openstack-ceilometer-2015.1.3-3.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-07 05:31:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1465550 0 None None None Never
OpenStack gerrit 195343 0 None None None Never
OpenStack gerrit 203658 0 None None None Never

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.
Note You need to log in before you can comment on or make changes to this bug.