Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Editing disks for a virtual machine in the VM setting in vSphere client is impossible No alert displayed but the options are greyed out in the VM configuration wizard as shown below: /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log contains the following entries: [2021-09-20T16:09:26.596+02:00] [WARN ] data-service-pool-673 70007704 100209 200011 com.vmware.vsan.client.util.VsanInventoryHelper No vSAN datastore found for VM ManagedObjectReference: type = VirtualMachine, value = vm-69082, serverGuid = 1692746b-6d70-44be-b585-738e1bc486b1 [2021-09-20T16:09:28.805+02:00] [ERROR] data-service-pool-786 70007709 100209 200011 c.v.v.c.spbm.impl.VmProfileAssignmentPropertyProviderAdapter Failed to retrieve VmStorageRollupComplianceResult: com.vmware.vsphere.client.spbm.impl.PbmServiceUnableToConnectException: java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.InvalidSslCertificateException: Invalid SSL certificate (HTTP 526 status code) at com.vmware.vsphere.client.spbm.impl.PbmServiceImpl.getServiceInstanceContent(PbmServiceImpl.java:89) at com.vmware.vsphere.client.spbm.impl.PbmServiceImpl.getComplianceManager(PbmServiceImpl.java:120) [...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.InvalidSslCertificateException: Invalid SSL certificate (HTTP 526 status code) at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:81) at com.vmware.vsphere.client.spbm.impl.PbmServiceImpl.getServiceInstanceContent(PbmServiceImpl.java:87) ... 17 common frames omitted Caused by: com.vmware.vim.vmomi.client.exception.InvalidSslCertificateException: Invalid SSL certificate (HTTP 526 status code) [...] [2021-09-20T16:09:28.813+02:00] [ERROR] data-service-pool-688 70007710 100209 200011 c.v.v.client.spbm.impl.VmReplicationGroupPropertyProviderAdapter Failed to invoke ReplicationManager.queryReplicationGroups()! com.vmware.vsphere.client.spbm.impl.PbmServiceUnableToConnectException: java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.InvalidSslCertificateException: Invalid SSL certificate (HTTP 526 status code) at com.vmware.vsphere.client.spbm.impl.PbmServiceImpl.getServiceInstanceContent(PbmServiceImpl.java:89) at com.vmware.vsphere.client.spbm.impl.PbmServiceImpl.getReplicationManager(PbmServiceImpl.java:111) [...]
The issue is caused by a mismatching SSL trust in the vCenter Server lookupservice.
Due to the required restart of the vCenter Services to fix trust mismatches in the lookupservice, a downtime is required. Please plan accordingly.
Note: Before taking any steps, please ensure to have a fresh backup of the vCenter Server.To resolve this issue, use the lsdoctor tool with the option -t (or --trustfix) to fix the mismatching SSL trust.After using the tool, restart the vCenter services using: # service-control --stop --all && service-control --start --all For further details regarding the lsdoctor tool, please see https://kb.vmware.com/s/article/80469
As a workaround you can use VMware PowerCLI to edit the virtual disk configuration (e.g. to increase the disk size)