BDA Mammoth 2.5 Upgrade Fails at Step 8 with Exec[enable_cm_alerts] and during pre-upgrade checks when TaskTrackers are Decommissioned (Doc ID 1670164.1)

Last updated on MAY 10, 2014

Applies to:

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

Symptoms

If TaskTrackers have been decommissioned on any nodes of a BDA cluster where HBase Region Servers are running (or for another reason) then during a Mammoth 2.5 upgrade two symptoms are observed:


1. During the pre-upgrade checks you will be
prompted with an error saying that the TaskTracker is not running on the decommissioned hosts. Since this is expected, hit continue when prompted (if this is the only error) and the upgrade will proceed.


During the pre-upgrade checks you will see:

ERROR: Tasktracker not running on node <....>

 

2. Step 8 of the upgrade will fail with the error below:


ERROR: Puppet agent run on node bdanode had errors. List of errors follows

************************************
Error [12177]: (//bdanode.example.com//Stage[main]//Node[default]/Exec[enable_cm_alerts]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.out returned 1 instead of one of [0] at /opt/oracle/BDAMammoth/puppet/manifests/site.pp:18

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms