Step 5 of Mammoth Upgrade Fails During "Installing Hadoop Parcel" Due to Parcel Upgrade Failure Caused by Failure to Deploy Client Configuration on a Host with HBase Role
(Doc ID 2277807.1)
Last updated on JANUARY 17, 2020
Applies to:Big Data Appliance Integrated Software - Version 4.7.0 and later
Step 5 of Mammoth upgrade fails during "Installing Hadoop Parcel". The failure is due to the CDH parcel upgrade failing because it can not deploy the client configuration on a node with HBase role.
Step 5 fails during "Installing Hadoop Parcel" with:
change from notrun to 0 failed:
/opt/oracle/BDAMammoth/bdaconfig/tmp/deployparcel_<EPOCH_TIMESTAMP>.out returned 1 instead of one of 
Additional symptoms include:
1. deployparcel_<EPOCH_TIMESTAMP>.out shows:
Result Message is: "Failed to upgrade cluster: <a target=\"_blank\" href=\"/cmf/hardware/hosts?filterHeartbeatHealth=bad\">1 host(s) that cannot be reached</a>. These hosts must be fixed, decommissioned, or removed from the cluster before upgrade can proceed.",
2. Navigating in CM to Hosts > Parcels shows the following error while upgrading the parcel:
3. Navigating in CM to Home > All Recent Commands shows the parcel upgrade failed on step 23 of 24 when trying to deploy the client configuration.
a) Manually deploying the client configuration in CM from Home > <CLUSTER_NAME> > dropdown > Deploy Client Configuration also fails with:
Completed only 7/8 steps. First failure: Client configuration (id=70) on host bdanode0x.example.com (id=2) exited with 2 and expected 0.
b) Drilling down into the logs show the deploying the client configuration fails due to an HBase role on the node.
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