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.
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).
This should now be fixed in the Origin Metrics.
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)
@jshaughn do you have a test case we can use to test this?
@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.