[
https://issues.apache.org/jira/browse/AMBARI-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335917#comment-15335917
]
Hudson commented on AMBARI-17255:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5102 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5102/])
AMBARI-17255 AMS collector not coming up in 2.5 cluster blueprint (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f936de2f0b099f4a5a0514d94f401dc0c0d463bf])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
*
ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_metrics_deviation.py
> 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)
