You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2017/09/12 13:26:00 UTC
[jira] [Commented] (AMBARI-21934) All config versions for a config
group are disabled right after renaming the config group
[ https://issues.apache.org/jira/browse/AMBARI-21934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162930#comment-16162930 ]
Andrii Babiichuk commented on AMBARI-21934:
-------------------------------------------
+1 for the patch
> All config versions for a config group are disabled right after renaming the config group
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-21934
> URL: https://issues.apache.org/jira/browse/AMBARI-21934
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.2
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21934_branch-2.6.patch, AMBARI-21934.patch
>
>
> - Create a new config group for a service, override few properties and save and restart required services
> - Goto manage config groups window and rename this config group
> - Save and once you are back at the configs page all config versions for this config group(renamed) are disabled.
> - If we check the configs history tab we can see that versions exist.
> - Navigating back to the configs page enables them too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)