[
https://issues.apache.org/jira/browse/AMBARI-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115151#comment-14115151
]
Aleksandr Kovalenko commented on AMBARI-7074:
---------------------------------------------
+1 for the patch
> Config History: unable to display a service config version in non-default
> group
> -------------------------------------------------------------------------------
>
> Key: AMBARI-7074
> URL: https://issues.apache.org/jira/browse/AMBARI-7074
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-7074.patch, record2.mov
>
>
> See the attached video for the current behavior (which is incorrect).
> * On HDFS > Configs page, 'hdfs111' config group is selected.
> * This shows all SCVs that belong to 'hdfs111' config group in white boxes,
> and SCVs that belong to the default config group in gray boxes (expected
> behavior).
> * Click on V10 (this belongs to 'hdfs111' group). The config group pulldown
> should remain 'hdfs111' and display the contents of V10 and highlight the V10
> box. However, this is not working currently.
> Possible reason:
> * In configs controller, we always load selected servcie config version
> first, then load Tags and Groups
--
This message was sent by Atlassian JIRA
(v6.2#6252)
