Getting "Datastore does not satisfy compatibility since it does not support one or more required properties. Datastore is mounted on more than one availability zones." when navigating to the storage policy affiliated with the VKS Clusters

Products

• VMware vCenter Server

Issue/Introduction

• There is a recurring "Deploy OVF package from Content Library to Resource Pool" tasks that appears on the vCenter Server UI.
  
  
• Unable to deploy new workload clusters.
  
  
• When navigating to the storage policy affiliated with the VKS Clusters, there are no compatible datastores available.
  
  
• All the concerned datastores show the following alert- "Datastore does not satisfy compatibility since it does not support one or more required properties. Datastore is mounted on more than one availability zones".
  
  
• On top of an existing healthy Supervisor Cluster, there is another supervisor which is either in an unhealthy state or stuck in "Removing".
  
  
• In /var/log/vmware/content-library/cls.log of the vCenter Server Appliance, the task associated with the OVF deployment complains of an "invalid value" present in the Datastore mapping parameters of the target profile. That target profile is the "storage profile" whose Managed Object Reference ID can be seen in the logs as below (highlighted in Bold)
  
  | WARN     | vmoperator-vm-akze-createOrUpdateVM | cls-simple-activity    | VcTaskService                 | Task not found, taskId=<Task-ID>, progress=100.
| DEBUG    | vmoperator-vm-akze-createOrUpdateVM | cls-simple-activity    | VdcsFutureResultCallback     | setting the future with value DeploymentResult (com.vmware.vcenter.ovf.library_item.deployment_result) => {
    succeeded = false,
    resourceId = <null>,
    error = ResultInfo (com.vmware.vcenter.ovf.library_item.result_info) => {
        errors = [OvfError (com.vmware.vcenter.ovf.ovf_error) => {
    category = INPUT,
    issues = <null>,
    name = DatastoreMappingParams.target_profile,
    value = <storage policy-MobRef-ID>,
    message = LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
        id = com.vmware.ovfs.ovfs-main.ovfs.invalid_ovf_parameter,
        defaultMessage = Invalid value for DatastoreMappingParams.target_profile: <storage policy-MobRef-ID>.,
        args = [DatastoreMappingParams.target_profile, <storage policy-MobRef-ID>],
        params = <null>,
        localized = <null>
    },
    error = <null>
}],
        warnings = [OvfWarning (com.vmware.vcenter.ovf.ovf_warning) => {
    category = INPUT,
    issues = <null>,
    name = ,
    value = ,
    message = LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
        id = com.vmware.ovfs.ovfs-main.ovfs.vmw_extra_config_accept_others,
        defaultMessage = The following extra configurations in the OVF package might pose security risks, and will be deployed to the target virtual machine: [guestinfo.vmservice.defer-cloud-init],
        args = [[guestinfo.vmservice.defer-cloud-init]],
        params = <null>,
        localized = <null>
    },
    error = <null>
}],
        information = []
    }
}

Environment

• VMware vSphere Kubernetes Service
• VMware vCenter Server

Cause

A datastore or a set of datastores can only be associated with one availability zone at the same time.

Resolution

To fix the issue

1. Wait for the completion of the supervisor cluster removal. In case it is stuck due to some reason, proceed with troubleshooting the cause of the same and take the necessary corrective action.
   
   
2. Once the supervisor is successfully removed, proceed with removing the "vSphere Zone" configuration associated with the second supervisor cluster. To do the same, navigate to the cluster object > Configure > vSphere Zones. Select the concerned vSphere Zone and click on "Remove Cluster" followed by removing the vSphere Zone itself.