[
https://issues.apache.org/jira/browse/AMBARI-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109166#comment-15109166
]
Hadoop QA commented on AMBARI-14740:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12783347/AMBARI-14740.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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4992//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4992//console
This message is automatically generated.
> Add params to alert definitions during ambari upgrade
> -----------------------------------------------------
>
> Key: AMBARI-14740
> URL: https://issues.apache.org/jira/browse/AMBARI-14740
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.2.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14740.patch
>
>
> We have many parameters for different alert dfeinitions. But these parameters
> will be available only when you are deploying new cluster. If you are
> upgrading to the last version of ambari, these params will be not available,
> because they were not added during ambari upgrade. We have no code in
> UpgradeCatalogs which should add all these params.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
