[
https://issues.apache.org/jira/browse/AMBARI-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110635#comment-15110635
]
Hudson commented on AMBARI-14740:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4204 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4204/])
AMBARI-14740. Add params to alert definitions during ambari (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8887eb175afdc0e9340647a83e0f02cddbfdb8b])
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
> 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)
