In these cases, user needs verify the list of nodes upgraded completely, kill the upgrade process, and restart the upgrade, which skip the upgrade for nodes that completed and proceeds with nodes on previous versions.
Below are the troubleshooting commands could help during this scenarios.
isi update --rolling --manual - Initiates rolling upgrade, manual option ask the user for confirmation before rebooting every nodeisi update --check-only Pre upgrade health checkcd /var/logls -l update*cat update_handler_2015-07-23_14:57:10.txt log file isi_for_array -s ps awux | grep update list the running update processisi_for_array -s killall -9 update Kill the current running update processisi_for_array date dispalys date of the clusterisi_readonlyisi readonlyisi auth error 54isi_for_array -n2 killall -9 isi_upgrade_d kill the upgrade processisi_for_array -s ps awux | grep isi_for_arrayssh isceist01-2isi_for_array -s uname -a | awk '{print $4}'isi update --rolling --manualisi_for_array -s ps awux | grep upgrade_disi_for_array -s killall -9 isi_upgrade_d Kill the upgrade processisi_for_array -s ps awux | grep upgrade_d list the current running processes by upgrade filterisi update --rolling --manual Initiate rolling upgrade
This came in handy for me today; thanks for posting... I did need to run the following though to kill the isi_upgrade_d procs.
ReplyDeleteisi services -a isi_upgrade_d disable