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

Hadoop QA commented on AMBARI-8047:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12678240/AMBARI-8047.patch
  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 tests.
                        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: 
https://builds.apache.org/job/Ambari-trunk-test-patch/421//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/421//console

This message is automatically generated.

> Configs are not editable
> ------------------------
>
>                 Key: AMBARI-8047
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8047
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8047.patch, AMBARI-8047_branch-1.7.0.patch
>
>
> 1. Perform clean install
> 2. change a config in yarn (to have v2)
> 3. click to view v1 (which is not editable, correct)
> 4. browse to any other services (which only have v1) and they are not 
> editable -- which is a problem
> You have to reload browser for this situation to clear



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

Reply via email to