[
https://issues.apache.org/jira/browse/AMBARI-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417443#comment-15417443
]
Hadoop QA commented on AMBARI-18118:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12823288/AMBARI-18118.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8384//console
This message is automatically generated.
> 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)
