[
https://issues.apache.org/jira/browse/AMBARI-14397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060230#comment-15060230
]
Hadoop QA commented on AMBARI-14397:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12777995/AMBARI-14397.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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4610//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4610//console
This message is automatically generated.
> Cluster deployment with exported blueprint with stack advisor enabled doesn't
> work
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-14397
> URL: https://issues.apache.org/jira/browse/AMBARI-14397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.3.0
>
> Attachments: AMBARI-14397.patch
>
>
> 1. Deploy a cluster using the UI or a brand new blueprint
> 2. Once the cluster is up and running export the blueprint (
> ?format=blueprint )
> 3. Deploy a new cluster using the previously exported blueprint. In cluster
> creation template enable the use of stack advisor:
> {code:java}
> "config_recommendation_strategy" : "ALWAYS_APPLY"
> {code}
> Ambari enters into a loop waiting for all cluster configuration types to
> reach TOPOLOGY_RESOLVED state. Ambari continuously logs error messages like
> {code:java}
> AmbariContext:412 - Config type ams-hbase-site not resolved yet, Blueprint
> deployment will wait until configuration update is completed
> {code}
> After 30 mins retry Ambari server eventually gives up and the cluster
> provisioning fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
