Abnormal Node Status After a Version Upgrade
Symptom
After the upgrade, the node status displayed on the Agent Manager page is Version unmatched or Offline.
Possible Cause
During the upgrade, incorrect node server authentication information is entered. As a result, the node fails to be upgraded.
Troubleshooting Procedure
- Run the following command to go to the tool installation directory. (/opt/DevKit is the default tool installation directory. Replace it with the actual directory.)
1cd /opt/DevKit/tools
- Run the following command to upgrade the node reporting the error:
1./upgrade.sh /home/DevKit-All-x.x.x-Linux-kunpeng.tar.gz
During the upgrade, enter the user name for adding the node, absolute installation path of the node, and absolute path of the SSH private key file and password/root user password for logging in to the node server to upgrade nodes reporting the error one by one.
If the preceding steps fail, perform the following steps. Otherwise, skip the following steps.
On the Agent Manager page, delete the nodes and add them again. If a node fails to be deleted on the WebUI, log in to the node server to manually uninstall the node.
To uninstall a node, perform the following steps:
- Use an SSH remote login tool to log in to the Linux CLI as the OS user.
Perform this step as the root user. If you log in as a common user, run the su command to switch to the root user.
- Run the following command to go to the node installation directory. (/opt/DevKit is the node installation directory. Replace it with the actual directory.)
1cd /opt/DevKit/tools
- Run the following command to uninstall the node:
1./agent_entry.sh
If the node fails to be uninstalled, manually delete the DevKit user and the /usr/bin/devkit, /home/devkit, and /opt/DevKit folders on the node.