ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21934) All config versions for a config group are disabled right after renaming the config group
Date Wed, 13 Sep 2017 11:19:00 GMT

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

Aleksandr Kovalenko commented on AMBARI-21934:
----------------------------------------------

committed to trunk and branch branch-2.6

> 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)

Mime
View raw message