[
https://issues.apache.org/jira/browse/AMBARI-18857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657650#comment-15657650
]
Hadoop QA commented on AMBARI-18857:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838567/AMBARI-18857.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9239//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9239//console
This message is automatically generated.
> Add Service wizard: Storm site configs related to Ambari metrics service are
> not displayed on ui
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18857
> URL: https://issues.apache.org/jira/browse/AMBARI-18857
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18857.patch
>
>
> This issue is result of storm site being scattered between Storm service and
> AMS service.
> Its highly recommended to avoid such scattering of config sites across
> services. Doing so requires special handling on FE and generates lots of new
> flows that needs to be tested.
> storm site should only belong and be packaged inside Storm service. If there
> are some configs of storm-site that needs to be added if AMS is present then
> stack advisor can be leveraged to achieve that objective
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
