I took a look at the API, but it wasn’t very clear how to use it to make the 
change.
So I went into the Postgres database and found the table containing the repo 
info
and updated the table. Seems to have worked.

Brian

On Mar 23, 2015, at 2:06 AM, Yusaku Sako <[email protected]> wrote:

> Hi Brian,
> 
> > I’ve managed to reconfigure it so that the baseUrl
> being used for the HDP repo is 
> http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.1.2.0.
> 
> Did you make this change directly on the file system or through the Ambari 
> API?
> Ambari will overwrite the URLs in the HDP repo file while adding hosts if you 
> modified the repo files directly on the file system.
> 
> Yusaku
> 
> 
> From: Brian Jeltema <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Wednesday, March 18, 2015 10:43 PM
> To: "[email protected]" <[email protected]>
> Subject: Re: cannot add hosts to an HDP 2.1.2.1 cluster
> 
> I’m still fighting this problem, though I’ve made some progress.
> 
> I’m running Ambari 1.6.0. I’ve managed to reconfigure it so that the baseUrl
> being used for the HDP repo is 
> http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.1.2.0.
> However, when I add a new host to the cluster, it is trying to install the 
> latest 2.1.7.0 package,
> which is not present in that repo. How can I force the new host to use the 
> 2.1.2.0 bits?
> 
> Thanks.
> Brian
> 
> 
> On Mar 16, 2015, at 11:07 AM, Brian Jeltema <[email protected]> 
> wrote:
> 
>> I have an existing cluster running HDP 2.1.2.1 When I tried to add hosts to 
>> that cluster, the
>> install fails:
>> 
>> Error: Cannot retrieve repository metadata (repomd.xml) for repository: 
>> HDP-2.1. Please verify its path and try again
>> 
>> It’s attempting to download the repo from 
>> 
>>    
>> http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.1.2.1/hdp.repo
>> 
>> There is a repo available for 2.1.2.0. Was the repo for 2.1.2.1 
>> intentionally removed?
>> What is the cleanest way to fix this?
>> 
>> Brian
> 

Reply via email to