[
https://issues.apache.org/jira/browse/AMBARI-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166989#comment-14166989
]
Hudson commented on AMBARI-7726:
--------------------------------
SUCCESS: Integrated in Ambari-branch-1.7.0 #52 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/52/])
AMBARI-7726. Incorrect behavior of creating config groups. (akovalenko)
(akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5383c9fca4d7afce2ad4ade8b87b4d9e7ffa51f6)
* ambari-web/app/controllers/main/service/info/configs.js
> Incorrect behavior of creating config groups
> --------------------------------------------
>
> Key: AMBARI-7726
> URL: https://issues.apache.org/jira/browse/AMBARI-7726
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 1.7.0
>
> Attachments: AMBARI-7726.patch, AMBARI-7726_branch-1.7.0.patch
>
>
> Is present two-node vagrant cluster with all started services.
> Steps:
> # Go to HDFS configs.
> # Create config group and assign one host to it.
> # Select created group and override "DataNode maximum Java heap size"
> property.
> # Create other config group and assign one host to it.
> Result: after close config groups manager was opened config tab for created
> group. "DataNode maximum Java heap size" property has default and first
> group's values, but does not has "Override" button.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
