[
https://issues.apache.org/jira/browse/AMBARI-17202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329465#comment-15329465
]
Hadoop QA commented on AMBARI-17202:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810373/AMBARI-17202.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7344//console
This message is automatically generated.
> Upgrading Ambari Causes Alert Fields Not To Save Thresholds
> -----------------------------------------------------------
>
> Key: AMBARI-17202
> URL: https://issues.apache.org/jira/browse/AMBARI-17202
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17202.patch
>
>
> When upgrading from earlier versions of Ambari, the alert definitions do not
> include some of the new parameters / connection timeout values which were
> added to the alert definitions. This is normally OK since the alert framework
> has sensible defaults of the values are not specified.
> However, it was observed on Ambari 2.2.2 that the web client wasn't able to
> properly render/save the values.
> STR:
> Install Ambari 2.2.0
> Upgrade to Ambari 2.2.2
> You should now have alert definitions, such as DataNode Web UI, which do not
> have a connection_timeout value.
> Navigate to the DataNode Web UI alert definition page and notice that you are
> not able to update and save the "Connection Timeout" property correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
