[
https://issues.apache.org/jira/browse/AMBARI-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-25069:
----------------------------------
Summary: Ambari writes Empty baseurl values written to Repo Files when
using a local repository causing stack installation failure (was: Ambari
wrties Empty baseurl values written to Repo Files when using a local repository
causing stack installation failure)
> Ambari writes Empty baseurl values written to Repo Files when using a local
> repository causing stack installation failure
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-25069
> URL: https://issues.apache.org/jira/browse/AMBARI-25069
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.3
> Reporter: Akhil S Naik
> Assignee: Akhil S Naik
> Priority: Major
> Labels: pull-request-available
> Attachments: Screen Shot 2018-12-26 at 10.12.29 AM.png, Screen Shot
> 2018-12-26 at 10.13.14 AM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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 :
> {code:java}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 37, in <module>
> BeforeInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 352, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_packages()
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/shared_initialization.py",
> line 37, in install_packages
> retry_count=params.agent_stack_retry_count)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py",
> 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/yum_manager.py", line
> 219, in install_package
> shell.repository_manager_executor(cmd, self.properties, context)
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", 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>
> or
> 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
> compromise:
> 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'
> stdout:
> {code}
> We can See that Ambari UI shows the empty baseURL in review step
> !Screen Shot 2018-12-26 at 10.12.29 AM.png|height=350,width=850!
> It also sends the empty Repo version while deploy stage
> !Screen Shot 2018-12-26 at 10.13.14 AM.png|height=350,width=850!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
