Community Articles
Find and share helpful community-sourced technical articles
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)

Problem Statement : when using a local repository, installation fails due to empty baseurls being written to the Ambari repository (even though local repository baseurl values were provided). The installation fails with below error :

Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/", line 37, in <module>
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/", line 352, in execute
  File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/", line 33, in hook
  File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/", line 37, in install_packages
  File "/usr/lib/ambari-agent/lib/resource_management/core/", line 166, in __init__
  File "/usr/lib/ambari-agent/lib/resource_management/core/", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/ambari-agent/lib/resource_management/core/", line 124, in run_action
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/", line 30, in action_install
    self._pkg_manager.install_package(package_name, self.__create_context())
  File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/", line 219, in install_package
    shell.repository_manager_executor(cmd,, context)
  File "/usr/lib/ambari-agent/lib/ambari_commons/", line 753, in repository_manager_executor
    raise RuntimeError(message)
RuntimeError: Failed to execute command '/usr/bin/yum -y install hdp-select', exited with code '1', message: 'Repository InstallMedia is listed more than once in the configuration
 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:
     1. Contact the upstream for the repository and get them to fix the problem.
    2. Reconfigure the baseurl/etc. for the repository, to point to a working
       upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work).
     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...
     4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
         yum-config-manager --disable <repoid>

            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.

        Note that yum will try to contact the repo. when it runs most commands,so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice
            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot find a valid baseurl for repo: HDP-3.1-repo-1
Command aborted. Reason: 'Server considered task failed and automatically aborted it'

We can See that Ambari UI shows the empty baseURL in review step :


It also sends the empty Repo version while deploy stage


Root cause :

Workaround :

This is a Javascript bug in ambari that happens when using local repository and there is no internet access to cluster

to workaround this


1) go to /usr/lib/ambari-server/web/javascipts

cd /usr/lib/ambari-server/web/javascripts

2) take backup of app.js

 cp app.js app.js_backup

3) edit the app.js

find out the line(39892) : onNetworkIssuesExist: function () {

Change the line from :

   * Use Local Repo if some network issues exist
  onNetworkIssuesExist: function () {
    if (this.get('networkIssuesExist')) {
      this.get('content.stacks').forEach(function (stack) {
            usePublicRepo: false,
            useLocalRepo: true


   * Use Local Repo if some network issues exist
  onNetworkIssuesExist: function () {
    if (this.get('networkIssuesExist')) {
      this.get('content.stacks').forEach(function (stack) {
        if(stack.get('useLocalRepo') != true){
            usePublicRepo: false,
            useLocalRepo: true

as per :

Later as you have already deployed the cluster we need to reset the cluster (Caution : this will erase all the configs you have created previously in Step6 and also the Hosts and services you have selected need to select again )

Command :

ambari-server reset

And hard reload the page and start the create cluster wizard again.

Incase you have already at Step 9 and cannot proceed with ambari-server reset (as it invovles lots of Configs being added again , the below steps are for you )

Preqrequesties : The cluster now is in Deployment step(step 9 ) and you have only retry button to press


1) Stop ambari-server

2) login to Database

3) use the below command to list out all the contents in repo_definition table :

 select * from repo_definition; 

4) you can see the base_url will be empty for the all the Rows in the table

5) Correct the base_url for every rows and update it using the command :

update repo_definition set base_url='<YOUR BASE URL>' where id=<THE CORESPONDING ID>;

for ex :

update repo_definition set base_url='' where id=9;

6) after correcting all the base_url columns in repo_definition table

7) start ambari, Login to UI and press retry button, The Installation will work as smooth as it can be.

Hope this helps.


Thanks @Akhil S Naik . Your post saved my day!

@Akhil S Naik . Amazing Document, Made may day too. :)
Thanks for sharing it

Very helpful!


It may be implied by "Later as you have already deployed the cluster we need to reset the cluster," but I had to add an additional step of removing the empty baseurl repositories that had been configured on the hosts. If this step isn't done, the error continues to appear because the repo configuration is still left over from the failed attempt. This can be done two ways:


# yum remove HDP-3.1-repo-1
# yum clean all


 And also by manually removing the repo file from `/etc/yum.repos.d/' and then running 


# yum clean all


at least for the RHEL 7 hosts we were on.

Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
2 of 2
Last update:
‎08-17-2019 05:16 AM
Updated by:
Top Kudoed Authors