@Matt Andruff This might not be the root cause, as HDP-UTILS.repo file is generated before posting the blueprint by Cloudbreak. The default value is specified in application.yml (under hdp.entries.2.6.repo.util, it's value is HDP-UTILS-1.1.0.21), are you sure have not accidentally overwritten this parameter with custom value under [cloudbreak-deployment]/etc? You can check in Cloudbreak database, you should see the value for : docker exec -it cbreak_commondb_1 psql -U postgres select * from clustercomponent where componenttype ='HDP_REPO_DETAILS' where cluster_id = [your-cluster-id]; You should see sg. like this in the attributes text: "util":{"repoid":"HDP-UTILS-1.1.0.21"... In the meantime, can you tell the exact version of Cloudbreak? Hope this helps! ... View more

@Matt Andruff What were the exact steps in CB shell for creating that cluster? Haven't you missed setting the "utilsRepoId" for "cluster create"? --utilsRepoId string Stack utils repoId (e.g. HDP-UTILS-1.1.0.21) Here is the documentation: https://github.com/hortonworks/cloudbreak/tree/master/shell Hope this helps! ... View more

@Marcel Fest From the logs, it looks like that your deployer VM does not have Internet access, which is mandatory to be able to communicate with the Cloud Providers. Deployer without Internet access is not supported. Hope this helps! ... View more

@Marcel Fest Could you please send me the output of the following? cbd doctor TRACE=1 cbd init ... View more

@soumya swain Have you checked this tutorial? It has some steps not listed in the official docs. ... View more

@Alex McLintock Good news is that Cloudbreak HDF support is going to be part of next release! In the meantime if you think your original question was answered, could you please consider accepting it? ... View more

@Vincent Wang It has a slightly different name than it is written in the tutorial: It is natural that it redirects to the Azure Portal as that is the launching point. The Sandbox can be searched for either version 2.4 or 2.5 from the Azure Portal, too: Hope this helps! ... View more

@Juhi Garg If you find my answer satisfactory, would you please consider accepting it? Thanks! ... View more

@Alex McLintock Unfortunately HDF integration in Cloudbreak is a work in progress now with a Blueprint configuration aspect as well as a Cloudbreak code modification aspect. If you are looking to demo just NiFi on an HDP cluster, then you can use this: https://github.com/abajwa-hw/ambari-nifi-service It is unsupported and not intended for production uses though. If you would like to install HDF 3.0 into an existing cluster, you can follow this tutorial. There is a separate tutorial for installing to a new cluster. Hope this helps! ... View more

@Lance Lierheimer I am afraid this use-case is not supported yet by Cloudbreak. If you have a Hortonworks Solution Engineer contact, he can file a feature request for this requirement. Hope this helps! ... View more

Then please share all Cloudbreak logs, because it is difficult to tell what went wrong otherwise. ... View more

@Chokri Ben Necib It looks like the cluster install polling times out, this might be due to other long-running recipes. You can try increasing the default values of 90 retry attempts (/5 sec) in Profile (then pls. do a cbd restart): export CB_MAX_SALT_NEW_SERVICE_RETRY=90 export CB_MAX_SALT_RECIPE_EXECUTION_RETRY=90 I've tried to reproduce the error with the same recipe, but my recipe had run successfully. This is the command which runs the recipe, you can check the logs in the EC2 instance under "/var/log/recipes": "sh -x /opt/scripts/pre/support-timeout-recipe 2>&1 | tee -a /var/log/recipes/pre-support-timeout-recipe.log && exit ${PIPESTATUS[0]}" Are you sure that you applied the recipe to all the hostgroups? E.g. the one with Ambari? Hope this helps! ... View more

@Chokri Ben Necib What kind of recipes (pre/post) would you like to run? Could you please send us the exception itself? It should be in cloudbreak log if you type: cbd logs cloudbreak ... View more

@Smart Solutions AFAIK, Knox uses EHCache, which can be configured further by placing a ehcache.xml file in an appropriate location in classpath as written here: <param> <name>main.cacheManager.cacheManagerConfigFile</name> <value>classpath:ehcache.xml</value> </param> The content of the config file is described here, with a concrete example here. You should check "timeToIdleSeconds" (defaults to 120 seconds). Hope this helps! ... View more

@Juhi Garg It is not clear for me based on your description if you have successfully set up a storage account and created a container before trying to use WASB (which is a prerequisite). Have you followed the steps detailed here? There is a very good walkthrough here! And finally, there is a good technical overview here. Hope this helps! ... View more

@George Meltser If my answer helped you solving your problem, would you mind consider accepting it? Thanks in advance! ... View more

@George Meltser What is the exact error message, have you managed to solve it? You might find some useful information about yum setup in the official Amazon FAQ here. Hope this helps! ... View more

@George Meltser As a first step, you should boot an Amazon Linux instance, and run all the commands on this machine after SSH-ing to it. You can do that with logging in to your AWS account, selecting EC2 service, click on "Launch instance" and select Amazon Linux. You should see sg. like this: After that, you should choose an instance with at least 16 gb of RAM and SSH to it if it is ready. You can find some additional documentation here. Hope this helps (if yes, would you consider accepting my response? :)) ... View more