[
https://issues.apache.org/jira/browse/AMBARI-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318495#comment-14318495
]
Robert Nettleton commented on AMBARI-9584:
------------------------------------------
For this change, there are no unit tests that would be feasible. The first
change involves modifying one of the config files in the stack definition, the
second change affects the Ambari UI.
I've manually verified the following with my patch applied:
1. That clusters with Ambari Metrics included can be started properly via
Blueprints.
2. That a cluster with Ambari Metrics can be started using the Ambari UI
wizards.
> Blueprint deployments fail with 500 server error (NullPointerException)
> -----------------------------------------------------------------------
>
> Key: AMBARI-9584
> URL: https://issues.apache.org/jira/browse/AMBARI-9584
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.0.0
>
> Attachments: AMBARI-9584.patch
>
>
> Blueprint deployments that include the new Ambari Metrics service are failing
> with a 500 Server Error being returned to the REST client that attempts to
> create a cluster based on a Blueprint.
> The following exception is seen in the ambari-server.log:
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.getConfigurationRequests(AbstractResourceProvider.java:386)
> at
> org.apache.ambari.server.controller.internal.ClusterResourceProvider.setConfigurationsOnCluster(ClusterResourceProvider.java:832)
> at
> org.apache.ambari.server.controller.internal.ClusterResourceProvider.setConfigurationsOnCluster(ClusterResourceProvider.java:762)
> at
> org.apache.ambari.server.controller.internal.ClusterResourceProvider.processBlueprintCreate(ClusterResourceProvider.java:502)
> at
> org.apache.ambari.server.controller.internal.ClusterResourceProvider.createResources(ClusterResourceProvider.java:154)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:289)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:75)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:36)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:103)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:72)
> at
> org.apache.ambari.server.api.services.ClusterService.createCluster(ClusterService.java:131)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> ...
> I'm working on a patch for this issue, and will be submitting the patch
> shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
