[
https://issues.apache.org/jira/browse/AMBARI-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334016#comment-15334016
]
Hadoop QA commented on AMBARI-17255:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810845/AMBARI-17255_1.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServiceComponentTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7372//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7372//console
This message is automatically generated.
> AMS collector not coming up in 2.5 cluster blueprint deployment
> ---------------------------------------------------------------
>
> Key: AMBARI-17255
> URL: https://issues.apache.org/jira/browse/AMBARI-17255
> Project: Ambari
> Issue Type: Bug
> Components: alerts, ambari-metrics, blueprints
> Affects Versions: 2.4.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17255_1.patch
>
>
> After updating the property timeline.metrics.service.webapp.address to
> 0.0.0.0:6188 (earlier it was localhost:6188), I am able to access metadata
> using the command curl http://host1:6188/ws/v1/timeline/metrics/metadata
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
