[
https://issues.apache.org/jira/browse/AMBARI-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175513#comment-14175513
]
Hadoop QA commented on AMBARI-7835:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675562/AMBARI-7835.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 1 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.controller.internal.ClusterControllerImplTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/245//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/245//console
This message is automatically generated.
> Blueprints exports fail after an upgrade from Ambari 1.6 to 1.7.0
> -----------------------------------------------------------------
>
> Key: AMBARI-7835
> URL: https://issues.apache.org/jira/browse/AMBARI-7835
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 1.7.0
>
> Attachments: AMBARI-7835.patch, AMBARI-7835_1.7.0.patch
>
>
> Exporting a Blueprint from a running cluster after an upgrade from Ambari 1.6
> to 1.7.0 currently fails.
> The REST API reports a server failure, and the ambari-server.log indicates
> that a NullPointerException occurs:
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer$Configuration.stripRequiredProperties(ClusterBlueprintRenderer.java:594)
> at
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer$Configuration.<init>(ClusterBlueprintRenderer.java:541)
> at
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.processConfigurations(ClusterBlueprintRenderer.java:210)
> at
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:158)
> at
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:120)
> at
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:731)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:197)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> 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.getCluster(ClusterService.java:81)
> This exception only seems to occur in the following scenario:
> 1. Install Ambari 1.6
> 2. Start an HDP cluster (2.1, others may also cause this) using the Ambari
> UI.
> 3. Upgrade Ambari to v1.7.0.
> 4. Attempt to export a Blueprint based on the cluster, and this will cause
> the exception.
> The Blueprint configuration processor is currently failing to process certain
> "emtpy" configuration elements that the Ambari UI adds in Ambari 1.6 but does
> not add in newer versions of the code.
> The Blueprint configuration processor should be updated to handle empty
> configuration groups, which are valid in Ambari.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
