ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17202) Upgrading Ambari Causes Alert Fields Not To Save Thresholds
Date Mon, 13 Jun 2016 23:25:57 GMT


Hadoop QA commented on AMBARI-17202:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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:


Test results:
Console output:

This message is automatically generated.

> Upgrading Ambari Causes Alert Fields Not To Save Thresholds
> -----------------------------------------------------------
>                 Key: AMBARI-17202
>                 URL:
>             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
> 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
> 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

View raw message