Help Center/ Cloud Container Engine/ User Guide/ Clusters/ Upgrading a Cluster/ Troubleshooting for Pre-upgrade Check Exceptions/ Node OS
Updated on 2025-07-17 GMT+08:00
View PDF
Share

Node OS

Check Items

Check whether the OS kernel version of the node is supported by CCE.

Solution

  • Case 1: The node image is not a standard CCE image.

    CCE nodes run depending on the initial standard kernel version specified when they are created. CCE has performed comprehensive compatibility tests based on this kernel version. A non-standard kernel version may lead to unexpected compatibility issues during a node upgrade and the upgrade may fail. For details, see High-Risk Operations and Solutions.

    Do not directly upgrade this type of nodes. Instead, reset the nodes to a standard kernel version and then upgrade the nodes.

  • Case 2: An image of a special version is defective.

    A EulerOS release 2.8 (Arm) image of v1.17 is used in the source version. Such an image is defective because the docker exec command will be affected after Docker is restarted. When the cluster version is upgraded, the Docker version will be updated and Docker will be restarted. To resolve this issue, do as follows:

    1. Empty and isolate the affected nodes before upgrading the cluster.
    2. Upgrade the version to v1.19 or later and reset the nodes to replace the image with one of a later version, for example, EulerOS release 2.9.
  • Case 3: A cluster contains a node running EulerOS 2.8 Arm, and the node use an Snt3 NPU. During the cluster upgrade, the error message "check node pool os error" or "node xxx with os xxx not support upgrade" is displayed.

    The node OS does not match the cluster version. CCE standard or Turbo clusters of v1.28 or later versions do not support EulerOS 2.8 Arm (which has reached EOS). The Snt3 Arm model supports up to EulerOS 2.8 Arm. As a result, the cluster cannot directly upgrade the node OS, leading to an error. To continue the upgrade, take the following steps:

    1. To continue to use NPUs, select the proper NPU model and OS by referring to Mappings Between Cluster Versions and OS Versions and Software Versions Required by Different Models. For details about the purchase process, see Lite Cluster Usage Process.
    2. Migrate the services on the faulty node to the node purchased in 1. For details, see Draining a Node.
    3. Delete the faulty node and upgrade the cluster again.
Parent Topic: Troubleshooting for Pre-upgrade Check Exceptions