BDA Expansion Fails On the "InstallHadoop" Step at Hadoop::Installpkg2/Package with "Could not get latest version"
(Doc ID 2476501.1)
Last updated on APRIL 17, 2023
Applies to:
Big Data Appliance Integrated Software - Version 4.5.0 and laterLinux x86-64
Symptoms
The BDA "InstallHadoop" step of expansion fails at Hadoop::Installpkg2/Package with "Could not get latest version".
The example here is from a BDA V4.5 cluster expansion where the failing "InstallHadoop" step is at Step 9. The example failures when "Installing Hadoop Packages" during the "InstallHadoop" step look like:
Error [73162]: (//bdanode01.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 [73162]: (//bdanode01.example.com//Stage[main]/Hadoop::Installpkg2/Package[cloudera-manager-daemons]/ensure) change from 5.7.0-1.cm570.p0.76.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 [73162]: (//bdanode01.example.com//Stage[main]/Hadoop::Installpkg2/Package[cloudera-manager-server]/ensure) change from 5.7.0-1.cm570.p0.76.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 [73162]: (//bdanode01.example.com//Stage[main]/Hadoop::Installpkg2/Package[ant]/ensure) change from 1.7.1-13.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):
Additional symptoms look like:
1. The associated puppet agent log file, /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdanode01-<timestamp>.log shows "Cannot retrieve repository metadata (repomd.xml)" messaging like:
for repository: cloudera-manager. Please verify its path and try again
bdanode01 puppet-master[73162]:
2. It is observed that the packages raising the complaints already exist on all existing cluster nodes. For example:
Cause
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
Symptoms |
Cause |
Solution |