Troubleshoot the upgrade process

This topic describes common problems and errors that occur during the upgrade process and how to identify and resolve them.

To check for multiple conflicting upgrades:

The upgrade command automatically checks for multiple ucp-worker-agents, the existence of which can indicate that the cluster is still undergoing a prior manual upgrade. You must resolve the conflicting node labels before proceeding with the upgrade.

To check Kubernetes errors:

For more information on anything that might have gone wrong during the upgrade process, check Kubernetes errors in node state messages after the upgrade is complete.

To circumvent the SLESS12 SP5 Calico CNI error:

Beginning with MKE 3.7.12, MKE cluster upgrades on SUSE Linux Enterprise Server 12 SP5 result in a Calico CNI Plugin Pod is Unhealthy error. You can bypass this error by manually starting cri-dockerd:

sudo systemctl start cri-dockerd-mke