cbd generate - exec: not started

Question

I followed this documentation to install Hortonworks cloudbreak.

Everything goes through fine as long as I create an instance on Azure and execute the commands specified.

Now I want to automate the installation of cloudbreak through Ansible. It's all simple commands, I could easily write the tasks in ansible but at the step cbd generate I see an error: "exec: not started"

This happens only when I am trying through ansible, If I try executing the commands manually, I can get the cloudbreak working.

I also tried using the shell module in ansible and copy paste the commands from the link and created the task. But it still gives the same problem. I am not able to proceed further from here.

• Ansible version: 2.4.2.0
• Cloudbreak Version: 2.7.0 (Latest is 2.7.1, We want to use 2.7.0)
• OS: Tried both on Centos 7.3 and 7.4
• Docker version: 1.13.1

Looking for a solution to this problem.

Answer 1

Issue was with Disc mount script I was using in Automation. These are the steps I was following for Automation:

1. Create centos 7.3 instance on azure through Terraform
2. Run Ansible playbook to perform disc mount and install Hortonworks cloudbreak

There was an issue with /etc/fstab entry for the data disc, which is updated by the disc mount script. So when I try to execute 'cbd' command outside the data disc it went through fine. If I execute the command inside the data disc (In my case I had mounted the data disc on the path /media, So whenever I change the directory to media and execute cbd I could see the error cbd: exec not found)

**I corrected the fstab entry like below:

UUID={uuid_name} /media ext4 defaults 0 0**

Script was updating like below:

UUID={uuid_name} /media ext4 noatime,nodiratime,nodev,noexec,nosuid 1 2

Really not sure what made cbd not to work with fstab entries. After changing it to defaults I am able to get the Cloudbreak deployer working through Ansible.