[jira] [Commented] (AMBARI-7726) Incorrect behavior of creating config groups

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-7726:
-----------------------------------

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

This message is automatically generated.

> Incorrect behavior of creating config groups
> --------------------------------------------
>
>                 Key: AMBARI-7726
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7726
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7726.patch, AMBARI-7726_branch-1.7.0.patch
>
>
> Is present two-node vagrant cluster with all started services.
> Steps:
> # Go to HDFS configs.
> # Create config group and assign one host to it.
> # Select created group and override "DataNode maximum Java heap size" property.
> # Create other config group and assign one host to it.
> Result: after close config groups manager was opened config tab for created group. "DataNode maximum Java heap size" property has default and first group's values, but does not has "Override" button.



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