During Upgrade The Step 2 Reboot Message Fails to List All Cluster Nodes as Requiring OS Kernel Update and Reboot
(Doc ID 2298371.1)
Last updated on FEBRUARY 22, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.4.0 and laterLinux x86-64
Symptoms
During Mammoth upgrade the OS kernel may be updated if the kernel is changing between releases. In Mammoth upgrades where the OS kernel is updated, it must be updated on all cluster nodes. The Step 2 Mammoth upgrade should output a message like below, listing all cluster nodes as requiring reboot to finalize the kernel upgrade.
INFO: Nodes to be rebooted: bdanode01,bdanode02,...bdanode0n
Proceed with reboot? [y/n]: y
In the case of the error condition not all cluster nodes are slated for reboot. The symptoms are:
1. On the first problem iteration only Node 1 will be slated for reboot. Phase 1 of the reboot step just updates Node 1. So in the case of the problem reported here it is not unexpected to see a request to only reboot Node 1. Output looks like:
INFO: Nodes to be rebooted: bdanode01
Proceed with reboot? [y/n]:
2. Depending on what steps were followed post the initial error condition of only Node 1 being slated for reboot, subsequent runs of "./mammoth -p" may show some combination of nodes missing from the reboot list. For example here bdanode06 is missing from the reboot list.
INFO: Nodes to be rebooted: bdanode02,bdanode03,bdanode04,bdanode05
Proceed with reboot? [y/n]: y
After reboot the kernel is only upgraded on the nodes listed for reboot, not on the node(s) missing from the list.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |