Have specified Ambari repo in Profile file export CB_JAVA_OPTS="-Dcb.ambari.repo.version=2.4.2.2-1 -Dcb.ambari.repo.baseurl=http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.5.0.0-513 -Dcb.ambari.repo.gpgkey=http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.5.0.0-513/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins" Cloudbreak is unable to setup Ambari. I see the following error in the log file. ^[[35mcloudbreak_1 |^[[0m Node: host-172-22-112-146.example.com Error(s): The following packages failed to install/update: ambari-agent=2.4.2.2-1 | Service ambari-agent is already enabled, and is dead | Parent directory not present | Parent directory not present | /etc/ambari-agent/conf/ambari-agent.ini: file not found | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/public_hostname.sh | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/internal_hostname.sh ^[[35mcloudbreak_1 |^[[0m Node: host-172-22-112-145.example.com Error(s): The following packages failed to install/update: ambari-agent=2.4.2.2-1 | Service ambari-agent is already enabled, and is dead | Parent directory not present | Parent directory not present | /etc/ambari-agent/conf/ambari-agent.ini: file not found | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/public_hostname.sh | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/internal_hostname.sh ^[[35mcloudbreak_1 |^[[0m Node: host-172-22-112-143.example.com Error(s): The following packages failed to install/update: ambari-server=2.4.2.2-1 | The following packages failed to install/update: ambari-agent=2.4.2.2-1 | Service ambari-agent is already enabled, and is dead | Service ambari-server is already enabled, and is dead | Parent directory not present | Command "cp -R /opt/jdbc-drivers /var/lib/ambari-server/jdbc-drivers" run | Parent directory not present | /etc/ambari-server/conf/ambari.properties: file not found | /etc/ambari-agent/conf/ambari-agent.ini: file not found | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/public_hostname.sh | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/internal_hostname.sh ^[[35mcloudbreak_1 |^[[0m Node: host-172-22-112-144.example.com Error(s): The following packages failed to install/update: ambari-agent=2.4.2.2-1 | Service ambari-agent is already enabled, and is dead | Parent directory not present | Parent directory not present | /etc/ambari-agent/conf/ambari-agent.ini: file not found | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/public_hostname.sh | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/internal_hostname.sh ^[[35mcloudbreak_1 |^[[0m Node: host-172-22-112-142.example.com Error(s): The following packages failed to install/update: ambari-agent=2.4.2.2-1 | Service ambari-agent is already enabled, and is dead | Parent directory not present | Parent directory not present | /etc/ambari-agent/conf/ambari-agent.ini: file not found | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/public_hostname.sh | One or more requisite failed: ambari.agent./etc/ambari-agent/conf/internal_hostname.sh, additional info: SaltJobIdTracker{saltJobRunner=HighStateChecker{BaseSaltJobRunner{target=[172.22.112.142, 172.22.112.144, 172.22.112.143, 172.22.112.146, 172.22.112.145], jid=JobId{jobId='20161223034848453213'}, jobState=FAILED}}} ^[[36mtraefik_1 |^[[0m time="2016-12-23T03:49:18Z" level=debug msg="Round trip: http://172.17.0.7:3000, code: 200, duration: 6.592445ms tls:version: 303, tls:resume:false, tls:csuite:c02f, tls:server:" Cloudbreak Deployer: 1.6.2-rc.18-92fb5f8 ... View more

document.txtI have setup cloudbreak on openstack and trying to create a cluster with hdp-small-default bp. The cluster comes up by there are issues with HDFS capacity. On Ambari, i see HDFS Capacity Utilization Capacity Used:[100%, 24576], Capacity Remaining:[0] alert. In the HDFS config, i see name node directory set to /hadoopfs/fs1/hdfs/namenode. Namenode is running on a host with 80 GB space on file system /dev/vda1 mounted on /. But /hadoopfs/fs1 is mounted on /dev/vdb which has just 9.8 GB of space. Not sure why its defaulting namenode dir to /hadoopfs/fs1/hdfs/namenode since the blueprint does not specify anything. Tried adding "properties": { "dfs.namenode.name.dir": "/grid/0/hadoop/hdfs/namenode", "dfs.datanode.data.dir": "/grid/0/hadoop/hdfs/data" } in hdfs-site properties globally and in all host groups but the default still points to /hadoopfs/fs1/hdfs/namenode attached is the blueprint i have used ... View more