Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

couldbreak unable to setup ambari

Solved Go to solution
Highlighted

couldbreak unable to setup ambari

New Contributor

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

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: couldbreak unable to setup ambari

Contributor

it seems the cb.ambari.repo.version=2.4.2.2-1 is wrong, it shuld be 2.5.0.0-513

View solution in original post

3 REPLIES 3
Highlighted

Re: couldbreak unable to setup ambari

Contributor

it seems the cb.ambari.repo.version=2.4.2.2-1 is wrong, it shuld be 2.5.0.0-513

View solution in original post

Highlighted

Re: couldbreak unable to setup ambari

New Contributor

Thanks @Peter Erdos, it worked.

Highlighted

Re: couldbreak unable to setup ambari

you could also do the same via cloudbreak shell using below command.

cluster create --version 2.X --stackRepoId HDP-2.X --stackBaseURL http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos7/2.x/BUILDS/2.X.X.0-154 --utilsRepoId HDP-UTILS-1.1.0.21 --utilsBaseURL http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos7 --stack HDP --verify true --os redhat7 --ambariRepoGpgKey http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.X.X.0-524/RPM-GPG-KEY/RPM-GP... --ambariRepoBaseURL http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.X.X.0-524 --ambariVersion 2.X.X.0-524 --enableSecurity true --kerberosMasterKey master --kerberosAdmin admin --kerberosPassword admin --wait true

Don't have an account?
Coming from Hortonworks? Activate your account here