Lily Web Server is Not Supported With BDA Upgrade or BDA Node Migration/Reprovision
(Doc ID 2143769.1)
Last updated on JUNE 12, 2021
Applies to:
Big Data Appliance Integrated Software - Version 3.0 and laterLinux x86-64
Symptoms
When a lily web server is in place it usurps the default BDA apache httpd web server and causes node upgrade/migration/reprovision failures. Remove the lily web server prior to BDA upgrade or BDA node migration/reprovison Mammoth actions.
Known issues
1. Node migration may fail at Step 9, InstallHadoop with logs on the Mammoth node showing errors like below. This can happen in the case of a broken rpm repository. For example if "yum clean all" has been used to clear the cache on a particular server, the lily web server prevents bda rpm updates on the node and these errors can ensue.
yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: bda.
Please verify its path and try again
2. Node reprovision fails at Step 3, PatchFactoryImage with errors like:
change from absent to latest failed:
Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y list ota4h' returned 1:
Error: Cannot retrieve repository metadata (repomd.xml) for repository bda. Please verify its path and try again.
Error [51674]: (//bdanode01.example.com//Stage[main]/Miscsetup::Patch_fimage/Package[bda]/ensure)
change from 4.2.0-3,el6 to latest failed:
3. After Node reprovision Oracle Linux is not upgraded.
Check for use of the lily web server
1. Download the repomd.xml file and check for the presence of lily.
For example use wget and examine the content:
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 |
Known issues |
Check for use of the lily web server |
Cause |
Solution |