Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 19 Oct 2016 18:22:58 +0000 (UTC)
From: "Xi Wang (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13013606.1476901347000.31371.1476901378317@Atlassian.JIRA>
In-Reply-To: <JIRA.13013606.1476901347000@Atlassian.JIRA>
References: <JIRA.13013606.1476901347000@Atlassian.JIRA> <JIRA.13013606.1476901347884@arcas>
Subject: [jira] [Created] (AMBARI-18639) Ambari UI does not allow to modify
 EMPTY threshold text of 'OK' and 'WARNING'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 19 Oct 2016 18:23:19 -0000

Xi Wang created AMBARI-18639:
--------------------------------

             Summary: Ambari UI does not allow to modify EMPTY threshold text of 'OK' and 'WARNING'
                 Key: AMBARI-18639
                 URL: https://issues.apache.org/jira/browse/AMBARI-18639
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.4.1, 2.5.0
            Reporter: Xi Wang
            Assignee: Xi Wang
            Priority: Critical
             Fix For: 2.5.0, 2.4.2


Ambari UI does not allow to modify threshold of *'OK'* and *'WARNING'* in ResourceManager WEB UI alert.

*Steps to reproduce:*

1. Remove threshold from WARNING/OK at alert of ResourceManager WEB UI 
2. Save 
3. Refresh Ambari UI and and the field is blank *- Expected*
4. Add any threshold string (may be the one that you removed) to WARNING/OK and then save 
5. Refresh Ambari UI. _Here is the problem._ *It shows just blank.* 
6. API /api/v1/clusters/young-hdp250/alert_definitions/44 shows blank too. 
- It's happening because the PUT call is sent empty.   
 !RM Web UI- Alert Definitioni.jpg|thumbnail! 

{code}
"critical" : { 
          "text" : "Connection failed to {1} ({3})" 
        }, 
        "ok" : { 
          "text" : "HTTP {0} response in {2:.3f}s" 
        }, 
        "warning" : { 
          "text" : "" 
        } 
{code}


*Workaround:*

Manual update using curl command works. 


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