[
https://issues.apache.org/jira/browse/AMBARI-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved AMBARI-12456.
------------------------------------
Resolution: Won't Fix
Individual build team comes up with their own pattern to distinguish daily
builds with build numbers - bn stands for build number. There is also a build
location that is build number independent but you run the risk of binaries
getting updated while deployment is going on. An Ambari deployment is expected
to name the file to ambari.repo e.g. this is what I use
{code}
wget -O /etc/yum.repos.d/ambari.repo original_repo_url{code}
Most public/validated releases will have the name as ambari.repo.
> Bad name for ambari repo
> ------------------------
>
> Key: AMBARI-12456
> URL: https://issues.apache.org/jira/browse/AMBARI-12456
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: Redhat / CentOS / Oracle
> Reporter: Constantin Ungureanu
> Labels: easyfix
> Fix For: 2.1.2
>
>
> "Choose an appropriate <ambari-repo-url> based on the platform used:
> (Redhat / CentOS / Oracle) 6
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.1.0-1409/ambaribn.repo
> (Redhat / CentOS / Oracle) 7
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos7/2.x/BUILDS/2.1.0-1409/ambaribn.repo";
> ambaribn.repo should be renamed ambari.repo because when installing, it tries
> to copy this file with scp and it fails thus resulting in failing to install
> ambari. Error looks something as:
> ...
> ERROR: Bootstrap of host c6401.ambari.apache.org fails because previous
> action finished with non-zero exit code (1)
> ERROR MESSAGE: Execute of '<bound method BootstrapDefault.copyNeededFiles of
> <BootstrapDefault(Thread-1, started daemon 139849329964800)>>' failed
> STDOUT: Try to execute '<bound method BootstrapDefault.copyNeededFiles of
> <BootstrapDefault(Thread-1, started daemon 139849329964800)>>'
> I renamed ambaribn.repo to ambari.repo in /etc/yum.repos.d/ and that solved
> this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
