Bug 1410109

Summary:	Alerting issue in Metrics 0.21
Product:	OpenShift Container Platform	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Hawkular	Assignee:	Matt Wringe <mwringe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peng Li <penli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aos-bugs, fsimonce, jshaughn
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1415833 (view as bug list)		Environment:
Last Closed:	2017-05-30 12:48:24 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:
Bug Depends On:
Bug Blocks:	1415833

Description Jay Shaughnessy 2017-01-04 13:30:47 UTC

Description of problem:
Metrics version 0.21 suffers from the alerting issue described by https://issues.jboss.org/browse/HWKALERTS-210.  OS should move to Hawkular Metrics 0.23 or higher to resolve the issue.

Comment 7 Jay Shaughnessy 2017-01-20 13:10:38 UTC

The fix for hwkalerts-210 has been backported to the 1.3.x line and is now released in Alerting 1.3.3.Final. A PR has been generated to have Alerting 1.3.3.Final in Metrics 0.21.6, which is targeted for the OS 3.4.x line.

So, to be clear, the alerting issue should be fixed when updating to Metrics 0.21.6 (or higher).

Comment 8 Matt Wringe 2017-01-26 15:36:54 UTC

This should now be fixed in the Origin Metrics.

Comment 9 Peng Li 2017-02-04 08:47:56 UTC

verified with hawkular metrics 3.4.1
metrics-hawkular-metrics   3.4.1               ea4c68d376ca        18 hours ago        1.5 GB

hawkular version is 0.21.6.Final-redhat-1
(Git SHA1 - 55b78140efed77aaa793579aac3e0ed7f15b72ad)

Comment 10 Matt Wringe 2017-02-06 14:46:30 UTC

@jshaughn do you have a test case we can use to test this?

Comment 11 Jay Shaughnessy 2017-02-06 16:28:58 UTC

@mwringe, we did not automate the recreate-steps on this BZ, the scripts were used to reproduce and validate.  We have since continued to enhance our overall cluster-profile integration tests, see  https://issues.jboss.org/browse/HWKALERTS-218 for recent enhancements.  These is no specific automation for this bug, we are backporting only the fix.