My Oracle Support Banner

The Cloudera Manager "Add Hosts Wizard" Fails to Successfully Add an Edge Node into the BDA Cluster After Removing it Prior to Upgrade (Doc ID 2213443.1)

Last updated on JANUARY 15, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.6.0 and later
Linux x86-64


NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

Prior to BDA Mammoth upgrade edge nodes which are part of the BDA cluster are removed from Cloudera Manager (CM). After upgrade, the edge nodes are added back into the upgraded cluster using: Instructions to Add a Non-BDA Node to CDH Cluster on Oracle Big Data Appliance 4.0 Release (Doc ID 1943912.1).

However, the "Add Hosts Wizard" which is used to add the edge node into the cluster fails with:

Add New Hosts to Cluster

Installation failed on all hosts.

0 of 1 host(s) completed successfully.

Uninstalled on 1 host(s) after installation failure.

Hostname IP Address Progress Status <IP_ADDRESS_EDGENODE> Installation failed. Failed to install cloudera-manager-agent package.




1. The "Start Roles on Hosts Command" shows:

Start Roles on Hosts Command

Step Context
Execute command Start on service hdfs
Skipped command HdfsStartWithFailovers because it is unavailable hdfs

Execue command Start on service Solr
Skipped command Start because it is unavailable Solr

Execute command Start on service yarn yarn
Skipped command Start because it is unavailable

Execute command Start on service hive hive
Skipped command Start because it is unavailable



2. Navigating in CM: Hosts > All Hosts shows a "red"/"bad" status for the edge node.

3. On the edge node the following is observed:

a) It is observed that CDH components point to a previous not the current version of the CDH packages. For example with an upgraded CDH of 5.8.2 packages point to CDH 5.5.1 versions. Output is like:

sentry -> /opt/cloudera/parcels/CDH-5.5.1-1.cdh5.5.1.p1168.923/bin/sentry
spark-conf -> /opt/cloudera/parcels/CDH-5.5.1-1.cdh5.5.1.p1168.923/etc/spark/conf.dist
hbase-indexer -> /opt/cloudera/parcels/CDH-5.5.1-1.cdh5.5.1.p1168.923/bin/hbase-indexer
beeline -> /opt/cloudera/parcels/CDH-5.5.1-1.cdh5.5.1.p1168.923/bin/beeline
flume-ng -> /opt/cloudera/parcels/CDH-5.5.1-1.cdh5.5.1.p1168.923/bin/flume-ng

b) The alternatives are found not to be set up correctly.



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.