Cannot edit virtual disk configuration in vSphere Client as options are greyed out and it reports 0 GB in vCenter GUI

Products

VMware vCenter Server

Issue/Introduction

The vCenter GUI is showing the disk size as 0 GB, which is preventing us from editing the virtual machine's disk in vSphere.
Able to expand VMDK size from ESXi host client and it also reports correct size of VMDK in ESXi host client.
No alert displayed but VM disk size is shown as 0GB and the options are greyed out in the VM configuration wizard as shown below:

Cause

vCenter server is having SSL Trust Mismatch issue which causing the size of VMDK not reporting correctly in vCenter GUI.

The issue is caused by a mismatching SSL trust in the vCenter Server lookupservice.

/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log contains the following entries:

[yyyy-mm-dd] [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 = xxxxxxx-xxx-xxx-xxxx-xxxxxx
[yyyy-mm-dd] [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)
[...]
[yyyy-mm-dd] [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)
        [...]

If you do not see the above errors in the logs or no mismatch upon running the lsdocter.py -t script, check if the vmware-sps services state.

Resolution

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.
root@################### :/tmp/lsdoctor-240201 ]# python lsdoctor.py -t

ATTENTION: You are running a reporting function. This doesn't make any changes to your environment.
You can find the report and logs here: /var/log/vmware/lsdoctor

YYYY-MM-DDTHH:MM:SS INFO main: You are reporting on problems found across the SSO domain in the lookup service. This doesn't make changes.
YYYY-MM-DDTHH:MM:SS INFO live_checkCerts: Checking services for trust mismatches...
YYYY-MM-DDTHH:MM:SS INFO generateReport: Listing lookup service problems found in SSO domain
YYYY-MM-DDTHH:MM:SS INFO generateReport: No issues detected in the lookup service entries for ################## (VC 7.0 or CGW).
YYYY-MM-DDTHH:MM:SS INFO generateReport: Report generated: /var/log/vmware/lsdoctor/##################.json
root@################### [ /tmp/lsdoctor-240201 ]#
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://knowledge.broadcom.com/external/article/320837/using-the-lsdoctor-tool.html

Workaround:

As a workaround you can use VMware PowerCLI/ESXi Host UI to edit the virtual disk configuration (e.g. to increase the disk size).

Additional Information

Impact/Risks:
Due to the required restart of the vCenter Services to fix trust mismatches in the lookupservice, a downtime is required. Please plan accordingly.

This issue is being checked by Diagnostics for VMware Cloud Foundation.

The check is as follows:

Product: vCenter
Log File: vsphere_client_virgo.log
Log Expression Check "ERROR" AND "Failed to" AND "Invalid SSL certificate (HTTP 526 status code)" .

//Impact of vmware-sps service being in shutdown state.

The vmware-sps service is responsible for managing the vSphere Profile-Driven Storage, which is used for managing storage policies and storage capabilities in vSphere. If the vmware-sps service is in a shutdown state, it can prevent the creation, cloning, or migration of virtual machines using storage policies. Additionally, it can also prevent the ability to apply storage policies to existing virtual machines.

According to the sources provided, when the vmware-sps service is not running or not accepting connections, it can cause the following issues:

Cloning a virtual machine or deploying a virtual machine from a template fails with the error: A general system error occurred: PBM error occurred during PreCloneCheckCallback: vmodl.fault.systemerror

When selecting the destination datastore during storage migration of VMs, error appears as "Cannot connect to profile-driven storage service."