Downgrade failing during system node revert-to command
Applies to
Issue
- Downgrade from 9.12.1P3 to 9.11.1P12 stopped on step "system node revert-to -node <node_name> -version 9.11" -
cluster::*> system node revert-to -node <node_name> -version 9.11 -check-only true
Warning: This command reverts cluster configuration ONLY. The File system on
every controller in the cluster must be reverted by running
"revert_to" from the nodeshell on every controller. Example: run local
revert_to 9.11
Do you want to continue? {y|n}: y
...
The management application is restarting as part of the revert process. Log in again to complete the revert task.
The management gateway server restarted. Waiting to see if the connection can be reestablished[<node_name>:spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 2914 exited as a result of signal normal exit (0). The subsystem will attempt to restart.
...
The management gateway server restarted. Waiting to see if the connection can be reestablished...
The management gateway server restarted. Waiting to see if the connection can be reestablished...
The management gateway server restarted. Waiting to see if the connection can be reestablished...
The connection with the management gateway server could not be reestablished.- The node then becomes unreachable:
cluster::*> system image show
Is Is Install
Node Image Default Current Version Date
-------- ------- ------- ------- ------------------------- -------------------
Warning: Unable to list entries on node <node_name1>. RPC: Couldn't make
connection [from mgwd on node "<node_name2>" (VSID: -1) to mgwd at
169.254.223.111]
<node_name2>
image1 false false 9.11.1P12
image2 true true 9.12.1P3
2 entries were displayed.
SP Event Logsseen from the second node:
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node <node_name2> has gone down unexpectedly.
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node <node_name2> has gone down unexpectedly.
[<node_name2>:callhome.clam.node.ooq:EMERGENCY]: Call home for NODE(S) OUT OF CLUSTER QUORUM.
[<node_name2>:clam.node.ooq:EMERGENCY]: Node (name=<node_name1>, ID=1000) is out of "CLAM quorum" (reason=heartbeat failure).
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node <node_name2> has gone down unexpectedly.
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node <node_name2> has gone down unexpectedly.
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node <node_name2> has gone down unexpectedly.
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node <node_name2> has gone down unexpectedly.
[<node_name2>:callhome.clam.node.ooq:EMERGENCY]: Call home for NODE(S) OUT OF CLUSTER QUORUM.
[<node_name2>:clam.node.ooq:EMERGENCY]: Node (name=<node_name1>, ID=1000) is out of "CLAM quorum" (reason=heartbeat failure).
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node ILDEBRUFASS3B has gone down unexpectedly.
[<node_name2>:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node ILDEBRUFASS3B has gone down unexpectedly.
The management gateway server restarted. Waiting to see if the connection can be reestablishedOct 24 13:43:09 [<node_name2>:spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 2915 exited as a result of signal normal exit (1). The subsystem will attempt to restart.
...
The management gateway server restarted. Waiting to see if the connection can be reestablished...
The connection with the management gateway server could not be reestablished.