[
https://issues.apache.org/jira/browse/AMBARI-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-3877:
-------------------------------------
Attachment: AMBARI-3877.patch
> Duplicate config-group action not duplicate configs
> ---------------------------------------------------
>
> Key: AMBARI-3877
> URL: https://issues.apache.org/jira/browse/AMBARI-3877
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 1.4.3
>
> Attachments: AMBARI-3877.patch
>
>
> Override like 3 configs in a config group and save. Now go to the {{Manage
> Config Groups}} dialog and select this group and click on {{Duplicate}}
> action. A popup with name and description pops up and hitting OK creates the
> duplicated config group.
> Though this duplicated config group has the correct name/description, it does
> not have the duplicated configs (3 that we overrode). When doing the POST
> call, we should populate the {{desired_configs}} to be the exact same as the
> source config-group.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
