There are no updates available in the "Updates tab" for the supervisor cluster on the vCenter Server

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Multiple supervisor clusters are present in a vCenter Server 
• A single supervisor cluster is on the older version 
• The supervisor control plane node is updated to the expected version however the "spherelet" is still at an older version. Verify via CLI by running the command on the supervisor control plane node: "kubectl get nodes -A"
• Upon checking the vum server logs in the vCenter Server:
  
  /var/log/vmware/upgrade/vum-server/vmware-vum-server.log 

yyyy-mm-ddThh:mm:ssZ  error vmware-vum-server[2763776] [Originator@6876 sub=ClusterApplySolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.ClusterApplySolutionTask ID:<id>. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.TaskError.GetNextHostToRemediateFailed<Failed getting host recommendation from DRS to enter maintenance mode for cluster '<cluster_name>'. Reason: 'This operation would violate a virtual machine affinity/anti-affinity rule.'.>
-->
yyyy-mm-ddThh:mm:ssZ  warning vmware-vum-server[12977] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
yyyy-mm-ddThh:mm:ssZ info vmware-vum-server[2763776] [Originator@6876 sub=PM.AsyncTask.ClusterApplySolutionTask{16390}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.TaskError.GetNextHostToRemediateFailed",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "<cluster_name>"
-->             },
-->             (vmodl.KeyAnyValue) {
-->                key = "2",
-->                value = "This operation would violate a virtual machine affinity/anti-affinity rule."
-->             }
-->          ],
-->          message = <unset>
-->       }
-->    ],
-->    reason = "vLCM Task failed, see Error Stack for details."
-->    msg = "{
-->     "data": null,
-->     "error_type": "ERROR",
-->     "messages": [
-->         {
-->             "args": [
-->                 "<cluster_name>",
-->                 "This operation would violate a virtual machine affinity/anti-affinity rule."
-->             ],
-->             "default_message": "Failed getting host recommendation from DRS to enter maintenance mode for cluster '<cluster_name>'. Reason: 'This operation would violate a virtual machine affinity/anti-affinity rule.'.",
-->             "id": "com.vmware.vcIntegrity.lifecycle.TaskError.GetNextHostToRemediateFailed"
-->         }
-->     ]
--> }"
--> }

Environment

vSphere Kubernetes Service

Cause

The spherelet version update is currently blocked because VM-Host affinity rules configured on the vCenter Server are preventing virtual machine migration, which in turn inhibits the ESXi hosts from entering maintenance mode.

Resolution

Disable the VM-Host affinity and anti-affinity rules for the virtual machines residing within the cluster to enable ESXi hosts to successfully enter maintenance mode and proceed with the necessary spherelet version update.