[
https://issues.apache.org/jira/browse/AMBARI-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602836#comment-14602836
]
Hadoop QA commented on AMBARI-12162:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12742092/AMBARI-12162.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 1 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/3280//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3280//console
This message is automatically generated.
> Error after renaming config group and creating new one with the same name
> -------------------------------------------------------------------------
>
> Key: AMBARI-12162
> URL: https://issues.apache.org/jira/browse/AMBARI-12162
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 2.2.0
>
> Attachments: AMBARI-12162.patch
>
>
> STR:
> 1. Install Ambari
> 2. Open configs page.
> 3. Open Manage Config Groups popup, create config group with name "1" and
> save.
> 4. Open Manage Config Groups popup, rename config group "1" to "2", create
> config group with name "1" and save.
> As a result server will return 409 conflict error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
