How to Handle a BDA Mammoth Upgrade Incorrectly Started on a Node other than Node 1 (Doc ID 2082598.1)

Last updated on NOVEMBER 30, 2015

Applies to:

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

Goal

On the BDA Mammoth upgrades must take place from Node 1 of the cluster. This note documents what to do in the case of incorrectly starting the upgrade on another node.

If the Mammoth upgrade is started on a node other than node 1 it will fail at an early phase with something like:

INFO: Starting puppet services (as needed) on all nodes
INFO: Running as root: /usr/bin/ssh -l root bdanode01 /opt/oracle/BDAMammoth/bdaconfig/tmp/startpuppet.sh
...
INFO: Running as root: /usr/bin/ssh -l root bdanode06 /opt/oracle/BDAMammoth/bdaconfig/tmp/startpuppet.sh
INFO: Signing certificates from puppet agents. This will take some time ...
ERROR: Operation timed out
ERROR: Some certificates not signed or certificate requests missing
ERROR: Certificate request for node bdanode01.example.com not received
...
ERROR: Certificate request for node bdanode06.example.com not received
ERROR: Cannot continue with install #Step 1#

 

Solution

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