I managed to fix the repo url issue and complete cluster deployment. I was going back to previous Ambari steps several times while setting up the cluster and looks like this caused several settings to not get updated to the latest values. I saw several issues in registering hosts and getting the latest settings. But these and the HDP.repo url got fixed by restarting the ambari-server, adding the correct base url in the "Advanced Repostory Options", and then going down the steps without changes.
But I'm curious- are the configuration values provided by users in each Ambari step appended to a config file on the server host? Or is it cached in cookies on the browser until the last *summary and deploy* step? On Wed, Mar 16, 2016 at 10:31 AM, Sumit Mohanty <[email protected]> wrote: > Do you mean, the HDP.repo file created by Ambari/Agents do not contain the > Repo BaseURL that was set via Select Stack -> Advanced Repository Options > URLs? Did you also set them while installing the cluster? > > > Can you provide the details on what is provided via "Select Stack -> > Advanced Repository Options URLs" and what value is written to HDP.repo? > ------------------------------ > *From:* Ganesh Viswanathan <[email protected]> > *Sent:* Wednesday, March 16, 2016 9:41 AM > *To:* [email protected] > *Subject:* Ambari - HDP.repo issue > > Hello- > I setup ambari-server with the local repository option (for HDP, > HDP-UTILS, Ambari repos). But when I start ambari-agents on other hosts in > the cluster and try to create a new cluster, I see "HDP.repo" show up newly > at "/etc/yum.repos.d/". The file contains localhost in the base url and > hence the setup fails. > > How does HDP.repo get created in the other hosts by ambari-agent? Does it > get the setting from the Select Stack -> Advanced Repository Options URLs? > How is the url cached and brought by the agent to the installation node? > > I'm installing Ambari 2.2.1.0 with HDP 2.4 on Oracle-7 Linux host. > > Thanks, > Ganesh > >
