[
https://issues.apache.org/jira/browse/AMBARI-11444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587604#comment-14587604
]
Hadoop QA commented on AMBARI-11444:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12739765/AMBARI-11444-2.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 3 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/3193//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3193//console
This message is automatically generated.
> Number Widgets: Empty threshold for 'Critical' still shows the value as
> Critical
> --------------------------------------------------------------------------------
>
> Key: AMBARI-11444
> URL: https://issues.apache.org/jira/browse/AMBARI-11444
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0.
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11444-2.patch, AMBARI-11444-2.patch,
> AMBARI-11444.patch
>
>
> This jira is to understand the expected behavior in the following case:
> Edit a number widget. Current value is 291 (critical). Edit the thresholds so
> that Warning is at 290 and leave critical to empty. The Preview still shows
> it as critical(red).
> From that configuration, as we understand once the value hits 290, it should
> be a warning until it hits the value present in the critical field. as
> critical is empty everything above 290 should be warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
