receipes do not running when cloudbreak 1.16 try to provision a cluster

[#1]

When trying to create a cluster with cloudbreak the following Error occurs: Orchestrator component SaltJobIdTracker failed to start. Does someone know How I can solve this Problem?

[#2]

Following is a screenshot of the error.

[#3]

Following is a screenshot of the error in the event history:error2.jpg

[#4]

@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

[#5]

it is a PRE recipe. It should set Proxy for Internet connection. in Attatchement you find also a section of the log.

[#6]

@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!

[#7]

@pdarvasi thank you for the hints. Unfortunatly, I could not find the order "/var/log/recipes". yes the recipe has been applied to all the hostgroups. I will try change the Profile as you mentioned.

[#8]

To your information. I use cloudbreak 1.16

[#9]

your solution does not work. I get the same error.

[#10]

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

[#11]

Hi @Chokri Ben Necib

The problem with the proxy configuration that we do not configure the proxy on the deployed clusters. If you want to configure it on your cluster then you should do it before the salt bootstrap. You should define this variable and then write your script into that, to configure the proxy settings on the cluster:

-Dcb.customData

you can define it in you profile with:

export CB_JAVA_OPTS="-Dcb.customData='touch /tmp/testdata'"

in this case the variable which you define here is a script which will run before the bootstrap process so it will configure the proxy on the cluster.

Br, R

[#12]

@rdoktorics thanks. I tried the following statement and restarted cloudbreak. Unfortunately, cloudbreak does not work properly!! did I miss anything?

export CB_JAVA_OPTS="-Dhttp.proxyHost=webproxy.comp.db.de -Dhttp.proxyPort=8080 -Dhttps.proxyHost=webproxy.comp.db.de -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=172.17.0.1|*.service.consul|*.node.dc1.consul -Dcb.customData='sudo echo proxy=http://webproxy.comp.db.de:8080 >> /etc/yum.conf'"