You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2014/10/10 16:24:33 UTC
[jira] [Updated] (AMBARI-7726) Incorrect behavior of creating
config groups
[ https://issues.apache.org/jira/browse/AMBARI-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Kovalenko updated AMBARI-7726:
----------------------------------------
Attachment: AMBARI-7726.patch
> 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
>
>
> 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)