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/24 20:29:34 UTC
[jira] [Resolved] (AMBARI-7956) It is not possible to remove custom
config group with linked host on EC2 (+external host names instead
internal)
[ https://issues.apache.org/jira/browse/AMBARI-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Kovalenko resolved AMBARI-7956.
-----------------------------------------
Resolution: Fixed
> It is not possible to remove custom config group with linked host on EC2 (+external host names instead internal)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-7956
> URL: https://issues.apache.org/jira/browse/AMBARI-7956
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-7956.patch, AMBARI-7956_branch-1.7.0.patch
>
>
> Steps:
> # Go to any (HDFS, for example) service.
> # Add custom config group.
> # Link one host to created config group.
> # Try to remove created config group.
> Result: group is still present, error in console.
> Note: in manage config groups are displayed external hostnames, but at local machines are displayed internal always.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)