[
https://issues.apache.org/jira/browse/AMBARI-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183336#comment-14183336
]
Hudson commented on AMBARI-7956:
--------------------------------
SUCCESS: Integrated in Ambari-branch-1.7.0 #206 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/206/])
AMBARI-7956. It is not possible to remove custom config group with linked host
on EC2 (+external host names instead internal). (Denys Buzhor via akovalenko)
(akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=32e08df543a163cf4c1eabd309a043858dfc068d)
*
ambari-web/test/controllers/main/service/manage_config_groups_controller_test.js
* ambari-web/app/controllers/main/service/manage_config_groups_controller.js
* ambari-web/app/assets/test/tests.js
> 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)