Node Reprovision Known Issues on BDA 4.13 and Higher
(Doc ID 2862885.1)
Last updated on APRIL 17, 2023
Applies to:Big Data Appliance Integrated Software - Version 4.13.0 and later
Known issues which can be encountered during node reprovision on BDA V4.13 and higher.
Anyone doing a node reprovision on BDA V4.11 and higher.
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
|If reprovisioning a node into a cluster with CA signed certificates open an SR with Oracle Support before performing the reprovision.|
|If an SR is not opened with Support prior to performing reprovision custom certificates can be overwritten during StartHadoopServices.|
|Node Decommission Known Issues also Apply to Node Reprovision.|
|Node Reprovision Can Fail During Step 1 PreinstallChecks, when "Performing Base Image Version Checks on all nodes".|
|Node Reprovision Can Fail During Step 6, SetupKDC with "Error code 1 when executing changekrb5_newnodes.sh on host <HOSTNAME_REIMAGED_NODE>".|
|Node Reprovision Can Fail During Step 7, InstallHadoop if MySQL Replication is Not Enabled.|
|Node Reprovision Does a Cluster Restart During Step 8, StartHadoopServices.|
|Reprovision CleanupInstall Step May Report Errors about oracleUser.sh and hdfsUser.sh.|
|Post Node Reprovision Cloudera Manager May Report the Host in "Maintenance" Mode.|