ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-11193) Configs: edited a toggle and control reverts
Date Sun, 17 May 2015 02:13:59 GMT


Hadoop QA commented on AMBARI-11193:

{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:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:
Console output:

This message is automatically generated.

> Configs: edited a toggle and control reverts
> --------------------------------------------
>                 Key: AMBARI-11193
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Richard Zang
>            Assignee: Richard Zang
>             Fix For: 2.1.0
>         Attachments: AMBARI-11193.patch
> 1) edited the YARN pre-emption toggle in escape hatch
> 2) put in bogus info
> 3) the ui (correctly) would not let out of escape hatch
> 4) saved config w/o warning (i would have thought it would have validated this is bogus?)
> 5) then when the ui refresh, the ui was out of escape hatch (which should have been impossible
because the value was bogus)
> 6) if I escape hatch again, bogus value is there
> Seem two problems:
> - expected some warning this value is bogus for the config, especially these true/false
> - expected the ui to realize the value is bogus and not revert to non-escape hatch mode

This message was sent by Atlassian JIRA

View raw message