[
https://issues.apache.org/jira/browse/AMBARI-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417774#comment-15417774
]
Hudson commented on AMBARI-18118:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5509 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5509/])
AMBARI-18118. AlertDefinitionCommand intermittently provides stale
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=51bad4583b8efd8e7d8e43bd566ae65393908077])
*
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionHashTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/agent/AlertDefinitionCommand.java
> AlertDefinitionCommand intermittently provides stale configurations
> -------------------------------------------------------------------
>
> Key: AMBARI-18118
> URL: https://issues.apache.org/jira/browse/AMBARI-18118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-18118.patch
>
>
> Existing code basically does that:
> takes all config versions that ever existed, iterates them in random order,
> and the config that happened to be last gets into final configuration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
