[
https://issues.apache.org/jira/browse/AMBARI-11665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571906#comment-14571906
]
Hudson commented on AMBARI-11665:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2803 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2803/])
AMBARI-11665. AMS : IllegalArgumentException populating metrics for host with
no cluster association. Unit test fixed. (swagle) (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=01f70297665b92c031c774fbc438f700fb2507cf)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
> AMS : IllegalArgumentException populating metrics for host with no cluster
> association
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-11665
> URL: https://issues.apache.org/jira/browse/AMBARI-11665
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11665.patch
>
>
> IllegalArgumentException when calling host API that includes host with no
> cluster association.
> {code}
> http://c6401.ambari.apache.org:8080/api/v1/hosts/c6403.ambari.apache.org
> {
> "status" : 400,
> "message" : "Invalid Request: Invalid arguments, cluster name should not be
> null"
> }
> {code}
> The agent is running on {{c6403.ambari.apache.org}}, but it has not been
> added to the cluster.
> In the stack trace ...
> {code}
> java.lang.IllegalArgumentException: Invalid arguments, cluster name should
> not be null
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.getConfigurations(AmbariManagementControllerImpl.java:1076)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.getConfigurations(AmbariManagementControllerImpl.java:2683)
> at
> org.apache.ambari.server.controller.internal.ConfigurationResourceProvider$2.invoke(ConfigurationResourceProvider.java:154)
> at
> org.apache.ambari.server.controller.internal.ConfigurationResourceProvider$2.invoke(ConfigurationResourceProvider.java:151)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.getResources(AbstractResourceProvider.java:302)
> at
> org.apache.ambari.server.controller.internal.ConfigurationResourceProvider.getResources(ConfigurationResourceProvider.java:151)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getDesiredConfigMap(AbstractProviderModule.java:800)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getCollectorPortName(AbstractProviderModule.java:287)
> at
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProvider.getMetricsRequests(AMSPropertyProvider.java:411)
> at
> org.apache.ambari.server.controller.metrics.timeline.AMSPropertyProvider.populateResourcesWithProperties(AMSPropertyProvider.java:345)
> at
> org.apache.ambari.server.controller.metrics.MetricsPropertyProvider.populateResources(MetricsPropertyProvider.java:127)
> at
> org.apache.ambari.server.controller.metrics.MetricsPropertyProviderProxy.populateResources(MetricsPropertyProviderProxy.java:170)
> {code}
> ... it looks like the AMS is trying to populate the metrics for the host and
> it calls an internal method that expects the host to be associated with a
> cluster.
> STR :
> # Create a cluster with AMS.
> # Install ambari-agent on host that is not currently in cluster and set
> hostname in its /etc/ambari-agent/conf/ambari-agent.ini
> # call API to get hosts at root level
> {{http://c6401.ambari.apache.org:8080/api/v1/hosts/c6403.ambari.apache.org}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
