BDA Mammoth OEL 5.8 upgrade hangs at Step 3 Patching the Factory Image (Doc ID 1903728.1)

Last updated on JULY 02, 2014

Applies to:

Big Data Appliance Integrated Software - Version 2.0.1 to 3.0.1 [Release 2.0 to 3.0]
Linux x86-64

Symptoms

An OEL 5.8 BDA upgrade, any BDA version may experience one of two symptoms:

1. Servers can appear to hang at Step 3 of the Mammoth upgrade, Patching the Factory Image.  It may appear that the reboot is taking a very long time.

2.  Mammoth may generate an error like:

INFO: Patching factory image. This will take some time ...
INFO: Puppet script successfully sent to node bdanode01
...
INFO: Puppet script successfully sent to node bdanode0n
INFO: Pinging puppet agents ...................
ERROR: Some puppet agents are not reachable
ERROR: Puppet agent on node bdanode0x is not reachable
ERROR: Cannot continue with install #Step 2#
INFO: Time spent in step 2 PatchFactoryImage is 1863 seconds.
INFO: Running bdadiagcluster...
INFO: Starting Big Data Appliance diagnose cluster at Fri May 30 18:45:04 2014
INFO: Logging results to /tmp/bda_diagcluster_1401500704.log

In the case here the node is generally unavailable. Pinging the Infiniband IP of bdanode0x fails:

 

3. Upgrading from BDA V2.0.1 or BDA V2.2.0 to BDA V2.3.1 may have similar symptoms as described in: BDA Mammoth 2.0.1 or 2.2.0 upgrade to 2.3.1 hangs at Step 3 Patching the Factory Image (Doc ID 1671584.1).

 

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