[
https://issues.apache.org/jira/browse/AMBARI-16097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257999#comment-15257999
]
Hudson commented on AMBARI-16097:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4738 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4738/])
AMBARI-16097. Duplicated config groups after renaming not saved group
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ee4dfb96337e05ed177e1783335c0c347cded96d])
* ambari-web/app/controllers/main/service/manage_config_groups_controller.js
> Duplicated config groups after renaming not saved group
> -------------------------------------------------------
>
> Key: AMBARI-16097
> URL: https://issues.apache.org/jira/browse/AMBARI-16097
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16097.patch
>
>
> SRT:
> 1. Open Manage Config Groups popup.
> 2. Create config group. Do not save changes.
> 3. Rename config group. Save Changes.
> After opening popup again you will see two config groups with the same
> name.Duplicated config groups after renaming not saved group
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
