Key Node Commands

Check Items

Whether some key commands that the node upgrade depends on are working

Solution

• Scenario 1: The RPM package manager command fails to be executed.

  The rpm command fails to be executed. In this case, log in to the affected node and check whether the following command is available:

  rpm -qa

  If the preceding command is unavailable, run the following command:

  rpm --rebuilddb

  If the fault persists, reset the node. For details, see Resetting a Node.

• Scenario 2: The dpkg package manager command fails to be executed.
  The dpkg command fails to be executed. In this case, log in to the affected node and check whether the following command is available:

  dpkg -l

  If the command is unavailable, reset the node. For details, see Resetting a Node.

• Scenario 2: The systemctl status command fails to be executed.

  If the systemctl status command on a node is unavailable, many check items will be affected. Log in to the node and check the availability of the following commands:

  systemctl status kubelet

  If the systemctl command cannot be used, reset the node. For details, see Resetting a Node.