[ 
https://issues.apache.org/jira/browse/AMBARI-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336581#comment-14336581
 ] 

Hadoop QA commented on AMBARI-9793:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12700772/AMBARI-9793.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:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/1809//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/1809//console

This message is automatically generated.

> Alert Definition: Thresholds are empty after edit
> -------------------------------------------------
>
>                 Key: AMBARI-9793
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9793
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.0.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9793.patch, AMBARI-9793_branch-2.0.0.patch, 
> after_save.PNG, definition_edit.PNG
>
>
> Steps to reproduce:
> # Fill in Thresholds as shown on [^definition_edit.PNG].
> # Hit save.
> # Go back to alerts table.
> # return to the edited alert ([^after_save.PNG]).
> Actual result:
> Threshold fields are empty.
> Expected result:
> Threshold fields have entered values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to