Mammoth Migration for the Host with Cloudera Manager Fails on Step 2, SetupMySQL, Installing the Correct meb RPM
(Doc ID 2860826.1)
Last updated on APRIL 17, 2023
Applies to:
Big Data Appliance Integrated Software - Version 4.13.0 and laterx86_64
Symptoms
Performing a mammoth migration for the host with Cloudera Manager (CM) role, Node 3 by default following:
Node 3 Migration and Recommission on Oracle Big Data Appliance V4.11 and Higher (Doc ID 2524859.1)
or
Node 3 Migration and Reprovision on Oracle Big Data Appliance V4.1 OL6 Hadoop Cluster to Manage a Hardware Failure (Doc ID 1984854.1)
fails in Step 2, SetupMySQL, with errors like below:
...
INFO: Setting up MySQL databases. This will take some time ...
...
ERROR: Puppet agent run on node <HOSTNAME_TARGET_CMHOST> had errors. List of errors follows
************************************
Error [71173]: (//<HOSTNAME_TARGET_CMHOST>.<DOMAIN>//Stage[main]/Mysql::Installmysql/Package[mysql-backup]/ensure) change from absent to latest failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install meb' returned 1: No Presto metadata available for bda
************************************
1. This error is raised on BDA OL7 clusters where the cluster was migrated from OL6 to OL7.
2. Checking for the meb package on the affected target OL7 host with "yum list all" finds the OL6 package:
4. Checking the following on the target host finds everything to be correct:
a) The bda repositories in /etc/yum.repos.d are correct.
b) The bda repo in /etc/yum.repos.d/bda.repo is correct.
c) /etc/yum.conf is correct and contains no proxies/etc.
5. The correct OL7 meb rpm, like meb.x86_64 4.1.0-el7 rpm, on BDA 4.13, exists on the Mammoth node, Node 1 by default, in the expected locations. For a host which has been migrated from OL6 to OL7 (based on BDA 4.13) those locations are:
- /opt/oracle/BDAPackages-ol7-4.13.0/Extras/MYSQL-COMMERCIAL-BACKUP/meb-4.1.0-el7.x86_64.rpm
- /opt/oracle/os_upgrade/BDAMammoth/bdarepo/RPMS/x86_64/meb-4.1.0-el7.x86_64.rpm
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 |
References |