Troubleshooting Errors Accessing the Yum Repository on the BDA Mammoth Node of the Cluster During Node Reprovision/Migration and in General
(Doc ID 2143787.1)
Last updated on JUNE 12, 2021
Applies to:
Big Data Appliance Integrated Software - Version 3.0 and laterLinux x86-64
Purpose
How to troubleshoot problems accessing the yum repository on the Mammoth node of the cluster during node migration/reprovision. The troubleshooting steps can be used any time there is a problem with access to the yum repository on the Mammoth node from another node.
In the example here Node 1 migration fails at Step 9, Install Hadoop, with:
INFO: Step 9 InstallHadoop
INFO: Acquiring run lock ...
INFO: Creating nodelist files...
...
Error [69931]: (//bdanode06.example.com//Stage[main]/Hadoop::Installpkg2/Package[cloudera-manager-agent]/ensure) change from 5.5.1-1.cm551.p0.8.el6 to latest failed: Could not get latest version: Execution of '/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py' returned 1: Traceback (most recent call last):
Error [69931]: (//bdanode06.example.com//Stage[main]/Hadoop::Installpkg2/Package[python-setuptools]/ensure) change from 0.6.10-3.el6 to latest failed: Could not get latest version: Execution of '/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py' returned 1: Traceback (most recent call last):
Error [69931]: (//bdanode06.example.com//Stage[main]/Hadoop::Installpkg2/Package[cloudera-manager-daemons]/ensure) change from 5.5.1-1.cm551.p0.8.el6 to latest failed: Could not get latest version: Execution of '/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py' returned 1: Traceback (most recent call last):
...
Based on these errors the Node 1 migration fails because packages can not be installed on Node 6. Further checking the logs on the Mammoth node shows errors of, "yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: bda." below for Node 6:
yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: bda.
Please verify its path and try again
Some causes for this could be a network connection issue (either a proxy (http or yum)) or a firewall.
Troubleshooting steps are below.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Purpose |
Troubleshooting Steps |