VM Edit settings in vSphere Client takes very long to load

Products

• VMware vCenter Server

Issue/Introduction

The VM Edit settings in the vSphere client takes a long time to load, whereas the same operation functions properly in the ESXi host client.

In /var/log/vmware/vpxd/vpxd.log:

YYYY-MM-DDTHH:MM:SSZ info vpxd[05983] [Originator@6876 sub=CryptoManager opID=q-139018:h5ui-getProperties:urn:vmomi:Folder:group-d1:46da153e-250f-47bc-9e82-a198b362f644:1319086174:VCenterKmipPropertyProvider:685777-2pop-h5:70015382-b9] The Vecs string entry 'clientKey-KMS' does not exist in VECS
YYYY-MM-DDTHH:MM:SSZ info vpxd[05954] [Originator@6876 sub=CryptoManager opID=q-139018:h5ui-getProperties:urn:vmomi:Folder:group-d1:46da153e-250f-47bc-9e82-a198b362f644:1319086174:VCenterKmipPropertyProvider:685777-2pop-h5:70015382-b9-WorkQueue-7f1c091a] The certificate entry 'clientKey-KMS' does not exist in VECS

In /var/log/vmware/vsphere-ui/logs/dataservice.log

[YYYY-MM-DDTHH:MM:SSZ] [WARN ] data-service-pool-781        70011190 100165 200023 ServicePropertyProviderAdapter [queryId: q-73089:h5ui-getProperties:urn:vmomi:Folder:group-d1:46da153e-250f-47bc-9e82-a198b362f644:1855508664] A PropertyProviderBean method's execution took too long: 120002 milliseconds. The method failed with an exception: null (Provider instance: com.vmware.vsphere.client.folder.impl.VCenterKmipPropertyProvider@3a562198, method: public com.vmware.vsphere.client.folder.keyServers.KmipClusterStatusSpec com.vmware.vsphere.client.folder.impl.VCenterKmipPropertyProvider.getH5DefaultKmipClusterStatus(com.vmware.vim.binding.vmodl.ManagedObjectReference) throws java.lang.Exception, property: ref: ManagedObjectReference: type = Folder, value = group-d1, serverGuid = 46da153e-250f-####-####-########, method args: [ManagedObjectReference: type = Folder, value = group-d1, serverGuid = 46da153e-250f-####-####-########])

Here, com.vmware.vsphere.client.folder.impl.VCenterKmipPropertyProvider execution took too long: 120002 milliseconds would mean that VM edit is timing out as there is no response from the key server.

Environment

VMware vCenter Server 8.x

Cause

The logs above indicate that there is a KMS with connectivity issues, or a KMS that is either inactive or decommissioned on the vCenter Server.

Example:

Resolution

• Login to vCenter Server -> Select the vCenter Object on the left -> Configure -> Security -> Key Providers.
• Please note that the status of the key providers on that screen will display as "unknown" for 3-4 minutes because of this issue.
• Fix the connectivity issues or remove the KMS.