[
https://issues.apache.org/jira/browse/AMBARI-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152166#comment-14152166
]
Anthony Penniston commented on AMBARI-6612:
-------------------------------------------
We notice this problem only after switching config versions. Switching between
config groups behaves as expected until a previous version of a config is
selected:
i.e.
1. go to HDFS -> Configs
2. make a modification (i.e. add a property 'foobar')
3. select different config groups
4. notice expected behavior
5. now select the config group in which the modification was made
7. select a previous version of that configuration
8. notice Add Property is hidden (as expected, since modifications cannot be
made to a previous version)
9. now toggle between different config groups
10. notice Add Property remains hidden, and the version list is in a bad state
(still showing versions for the previously selected config group)
expected behavior: when changing config groups, the version list and dropdown
should reflect that change and display versions for that config group.
> Add property button disappear after choosing config group
> ---------------------------------------------------------
>
> Key: AMBARI-6612
> URL: https://issues.apache.org/jira/browse/AMBARI-6612
> Project: Ambari
> Issue Type: Bug
> Components: site
> Affects Versions: 1.6.0
> Environment: RHEL6, Chrome 36.0.1985.125
> Reporter: Yixiao
> Assignee: Saman Alvi
> Labels: config, custom, web, webgui, xml
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When you have custom configuration groups, click the HDFS service's configs,
> it shows you the default config group. Expand custom hdfs-site.xml, it shows
> you a option of "add property".
> Choose your custom config group, the "add property" button disappear forever.
> It won't come back when you switch back to the default group.
> Reload the page to get the "add property" button back.
> This affects all the services with the Custom xxx-site.xml configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)