Unable to expand VMDK size, it reports 0 GB in vCenter GUI
search cancel

Unable to expand VMDK size, it reports 0 GB in vCenter GUI

book

Article ID: 374214

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Not able to expand size of VMDKs for all VMs of a cluster as the size reporting 0 GB in vCenter GUI when the menu for Hard-disk expanded.
  • Able to expand VMDK size from ESXi host client and it also reports correct size of VMDK in ESXi host client.
  • All VMs are accessible and using NFS datastores.

Environment

VMware vSphere ESXi 6.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

  • vCenter server is having SSL Trust Mismatch issue which causing the size of VMDK not reporting correctly in vCenter GUI.
  • Observed below instances in vCenter's vsphere_client_virgo.log and lsdoctor output.
vsphere_client_virgo.log :
[2024-08-08T11:45:13.436Z] [ERROR] data-service-pool-439        70000124 100005 200003 c.v.vsan.client.services.capability.VsanCapabilityCacheManager    (78f774f9c440) Cannot retrieve capabilities com.vmware.vsan.client.sessionmanager.vlsi.client.NotAccessibleException: Cannot connect to the specified site. The site might not be available on the network, or a network configuration problem might exist. Check your connection details and try again.
        at com.vmware.vsan.client.sessionmanager.vlsi.client.vc.VcClient.getConnection(VcClient.java:95)
        at com.vmware.vsan.client.sessionmanager.vlsi.client.vc.VcClient.getConnection(VcClient.java:72)
        at com.vmware.vsan.client.sessionmanager.vlsi.client.vc.VcClient.getConnection(VcClient.java:62)
        at com.vmware.vsan.client.sessionmanager.vlsi.client.vsan.VsanClient.getConnection(VsanClient.java:35)
        at com.vmware.vsan.client.services.capability.VsanCapabilityCacheManager$VsanTimeBasedCacheEntry.load(VsanCapabilityCacheManager.java:164)
        at com.vmware.vsan.client.services.capability.VsanCapabilityCacheManager$VsanTimeBasedCacheEntry.load(VsanCapabilityCacheManager.java:151)
        at com.vmware.vsphere.client.vsan.base.cache.TimeBasedCacheEntry.get(TimeBasedCacheEntry.java:36)
        at com.vmware.vsphere.client.vsan.base.cache.TimeBasedCacheManager.get(TimeBasedCacheManager.java:112)
        at com.vmware.vsan.client.services.capability.VsanCapabilityCacheManager.getHostCapabilities(VsanCapabilityCacheManager.java:72)
        at com.vmware.vsan.client.services.capability.VsanCapabilityUtils.getCapabilities(VsanCapabilityUtils.java:58)
        at com.vmware.vsan.client.services.capability.VsanCapabilityUtils.isIoInsightSupported(VsanCapabilityUtils.java:799)
        at com.vmware.vsphere.client.vsan.perf.VsanIoInsightPerfPropertyProvider.isIoInsightAvailableOnHost(VsanIoInsightPerfPropertyProvider.java:128)
        at com.vmware.vsphere.client.vsan.perf.VsanIoInsightPerfPropertyProvider.isIoInsightAvailableOnVM(VsanIoInsightPerfPropertyProvider.java:151)
        at com.vmware.vsphere.client.vsan.perf.VsanIoInsightPerfPropertyProvider.getResult(VsanIoInsightPerfPropertyProvider.java:80)
        at com.vmware.vsan.client.services.common.VsanBasePropertyProviderAdapter.getProperties(VsanBasePropertyProviderAdapter.java:49)
        at com.vmware.vise.data.query.impl.DataManager.getDataFromPropertyProvider(DataManager.java:1200)
        at com.vmware.vise.data.query.impl.DataManager.getResultFromPropertyProvider(DataManager.java:1167)
        at com.vmware.vise.data.query.impl.DataManager.access$000(DataManager.java:78)
        at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:931)
        at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:927)
        at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:826)
        at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:1240)
        at com.vmware.vise.data.query.impl.DataServiceThreadPoolDecorator$1.call(DataServiceThreadPoolDecorator.java:174)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain is not trusted and thumbprint verification is not configured
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:261)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.setResponseError(HttpExchangeBase.java:356)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.invokeWithinScope(HttpExchange.java:57)
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:31)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:57)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:227)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:114)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:693)

////////////////////////////////
root@###################[ /tmp/lsdoctor-240201 ]# python lsdoctor.py -l

    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

2024-08-08T12:19:50 INFO main: You are reporting on problems found across the SSO domain in the lookup service.  This doesn't make changes.
2024-08-08T12:19:51 INFO live_checkCerts: Checking services for trust mismatches...
2024-08-08T12:19:51 INFO generateReport: Listing lookup service problems found in SSO domain
2024-08-08T12:19:51 ERROR generateReport: default-first-site\################## (VC 7.0 or CGW) found SSL Trust Mismatch: Please run python ls_doctor.py --trustfix option on this node.
2024-08-08T12:19:51 INFO generateReport: Report generated:  /var/log/vmware/lsdoctor/########################.json
root@################### [ /tmp/lsdoctor-240201 ]#

Resolution

  • As vCenter reported SSL Trust Mismatch issue, took snapshot of the vCenter and ran trustfix using lsdoctor tool which fixed the SSL trust mismatch issue.

root@################### [ /tmp/lsdoctor-240201 ]# python lsdoctor.py -l

    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

2024-08-08T12:28:29 INFO main: You are reporting on problems found across the SSO domain in the lookup service.  This doesn't make changes.
2024-08-08T12:28:30 INFO live_checkCerts: Checking services for trust mismatches...
2024-08-08T12:28:30 INFO generateReport: Listing lookup service problems found in SSO domain
2024-08-08T12:28:30 INFO generateReport: No issues detected in the lookup service entries for ################## (VC 7.0 or CGW).
2024-08-08T12:28:30 INFO generateReport: Report generated:  /var/log/vmware/lsdoctor/##################.json
root@################### [ /tmp/lsdoctor-240201 ]#

  • After fixing the SSL trust mismatch on vCenter, vCenter GUI started reporting the VMDK size correctly and we were able to expand the VMDK size successfully.

Additional Information

Powered by Wolken Software