[
https://issues.apache.org/jira/browse/AMBARI-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319720#comment-14319720
]
Hadoop QA commented on AMBARI-9615:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12698655/AMBARI-9615.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1670//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1670//console
This message is automatically generated.
> Agents Do Not Update Cached Alert JSON On New Configurations
> ------------------------------------------------------------
>
> Key: AMBARI-9615
> URL: https://issues.apache.org/jira/browse/AMBARI-9615
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-9615.patch
>
>
> When an execution command is sent to an agent, it only checks to see if any
> of the existing alerts have configuration data changes. If none do, the
> updated configurations are not written to definitions.json.
> On an execution command, definitions.json shoudl always have its
> configuration section updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
