[
https://issues.apache.org/jira/browse/AMBARI-20802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976802#comment-15976802
]
Hadoop QA commented on AMBARI-20802:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12864273/AMBARI-20802_trunk.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 3 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11425//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11425//console
This message is automatically generated.
> StackAdvisor should not recommend configuration types for services that are
> not present in the cluster
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20802
> URL: https://issues.apache.org/jira/browse/AMBARI-20802
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20802_trunk.patch
>
>
> When a minimal Blueprint install was attempted in that issue, some failures
> occurred during the Blueprint deployment.
> After some investigation, we determined that the Blueprints processor was
> throwing a NullPointerException, due to some configuration types being
> considered "updated", even though those configuration types are not included
> in the "desired configuration" for the cluster, since the services associated
> with those configuration types are not deployed in this current cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
