BDA V4.3 Rolling Upgrade Fails to Reboot Node 1 After "Wrong OS disk s* partition" WARNINGS During Cluster Host Software Checks (Doc ID 2082080.1)

Last updated on JUNE 21, 2017

Applies to:

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

Symptoms


The symptoms follow:

1. The cluster host hardware checks of  the Mammoth V4.3 rolling upgrade raise WARNINGS like:

INFO: Starting cluster host software checks
bdanode01: Use of uninitialized value in numeric eq (==) at /opt/oracle/bda/bin/bdacommon.pm line 158.
bdanode01: WARNING: Wrong OS disk s0 partition info : 1 ext3 primary raid 2 ext3 primary raid 3 linux-swap primary 4 ext3 primary
bdanode01: INFO: Expected OS disk s0 partition info : 1 ext3 raid 2 ext3 raid 3 linux-swap 4 ext3 primary or 1 ext4 primary boot 2 primary raid 3 linux-swap(v1) primary 4 ext4 primary
bdanode01: Use of uninitialized value in numeric eq (==) at /opt/oracle/bda/bin/bdacommon.pm line 158.
bdanode01: WARNING: Wrong OS disk s1 partition info : 1 ext3 primary raid 2 ext3 primary raid 3 linux-swap primary 4 ext3 primary
bdanode01: INFO: Expected OS disk s1 partition info : 1 ext3 raid 2 ext3 raid 3 linux-swap 4 ext3 primary or 1 ext4 primary boot 2 primary raid 3 linux-swap(v1) primary 4 ext4 primary
bdanode01: WARNING: Wrong internal USB partitions : 1 ext3 primary
bdanode01: INFO: Expected internal USB partitions : 1 primary ext3 or 1 ext4 primary
bdanode01: WARNING: Big Data Appliance warnings during software validation checks
WARNING: Warnings during software checks on host bdanode01


2. bdacheckcluster is successful, but bdachecksw issues the same warnings.


3. Due to the warnings, Mammoth prompts with: "Do you want to continue" to which you should reply "yes":

Do you want to continue (yes/no):  yes


4. At Step 3, after the above warnings, Node 1 does not reboot.  Output looks like:

WARNING: The OS kernel was updated on some nodes - so those nodes need to be rebooted
INFO: Nodes to be rebooted: bdanode01,bdanode02,bdanode03,bdanode04,bda9node05,bdanode06
Proceed with reboot? [y/n]:y


INFO: Proceeding with rolling restart, critical nodes will be restarted first, then all others.
INFO: Restarting critical nodes bdanode02 bdanode03 bdanode04 one by one
INFO: Restarting node(s) bdanode02
.......
INFO: Restarting node(s) bdanode03
.......
INFO: Restarting node(s) bdanode04
INFO: Restarting non-critical bdanode05 bdanode06 two by two
INFO: Restarting node(s) bdanode05,bdanode06
Broadcast message from root (Wed Nov 18 18:17:30 2015):

The system is going down for reboot NOW!

Note there is no message about restarting Node 1.

5. After node reboot, logging into Node 1 shows output like:

a) Uptime shows Node 1 did not reboot:

b) No /root/BDA_REBOOT_SUCCEEDED is generated due to the initial warnings.  But checking Node 1 shows that no /root/bda_reboot_status or /root/BDA_REBOOT_WARNINGS is generated as is done on the other nodes of the cluster.


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