Upgrade to BDA V4.4 Fails After Step 2 Node Reboot when Executing checkSSHAllNodes.sh - Due to Corrupt Credentials Cache Files

(Doc ID 2116443.1)

Last updated on MARCH 15, 2016

Applies to:

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

Symptoms

During upgrade to BDA V4.4, after the BDA V4.4 Step 2 node reboot step, all the checks documented in Upgrading Oracle Big Data Appliance(BDA) CDH Cluster to V4.4.0 from V4.0.0, V4.1, V4.2, V4.3 Releases using Mammoth Software Upgrade Bundle for OL 5.8 or OL 6.4 (Doc ID 2101906.1), are successful.  However when resuming the upgrade the following is raised:

INFO: Executing checkSSHAllNodes.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step -1#
INFO: Error code 1 when executing checkSSHAllNodes.sh on host bdanode0x

Additional symptoms show:

1. It is possible to ssh to the host bdanode0x referenced in the INFO message above. However from bdanode0x it is not possible to ssh to any other cluster node.

2. Running ssh in verbose mode on bdanode0x, ssh -v bdanode0n, to ssh into any other node in the cluster reports:

debug1: Unspecified GSS failure. Minor code may provide more information
Cannot resolve network address for KDC in requested realm.

3. Running ssh in verbose mode, ssh -v, on any other node in the cluster reports:

debug1: Unspecified GSS failure. Minor code may provide more information
Matching credential not found

 

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