SDDC Manager UI Update page shows error - Unable to compute applicability for drift RemoveNfsDatastoreConfigDrift

Products

• VMware SDDC Manager

Issue/Introduction

When navigating to a specific Workload domain in the SDDC Manager UI, under Updates the following error message may be seen:

Retrieving configuration updates failed. Unable to compute applicability for drift RemoveNfsDatastoreConfigDrift. Because configuration realized check failed on resources [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx]. Please check logs and fix the failures of drift configuration realized checks. Then restart the service to trigger the configuration realized checks again and re-try the API. If this does not resolve the issue, please contact GSS.

 

In /var/log/vmware/vcf/domainmanager/domainmanager.log the below error is seen:

YYYY-MM-DDTHH:MM:SS.329+0000 INFO  [vcf_dm,67a5548dbf94a7ca61559ac718fb1965,fbf7] [c.v.v.c.service.ResourceCacheService,dm-exec-10]  Refresh failed configRealized check for drift xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx on resource xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
YYYY-MM-DDTHH:MM:SS.329+0000 INFO  [vcf_dm,0000000000000000,0000] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-537]  Refreshing live checks for DOMAIN with id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
YYYY-MM-DDTHH:MM:SS.329+0000 INFO  [vcf_dm,67a5548dbf94a7ca61559ac718fb1965,fbf7] [c.v.v.c.c.c.RemoveNfsDatastoreConfigDriftCheck,dm-exec-10]  Checking if NFS Datastore lcm-bundle-repo has been removed from all ESXi hosts in cluster with resource id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
YYYY-MM-DDTHH:MM:SS.329+0000 INFO  [vcf_dm,67a5548dbf94a7ca61559ac718fb1965,fbf7] [c.v.v.c.c.c.RemoveNfsDatastoreConfigDriftCheck,dm-exec-10]  Retrieving remote endpoints for ESXi hosts for cluster with resource id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx


YYYY-MM-DDTHH:MM:SS.632+0000 DEBUG [vcf_dm,67a5548ddb09a40c11c76e1209f02cd9,5afc] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-15]  Datastore with name lcm-bundle-repo not found on host esx01.domain.local 
YYYY-MM-DDTHH:MM:SS.632+0000 DEBUG [vcf_dm,67a5548ddb09a40c11c76e1209f02cd9,5afc] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-15]  Destroying 1 open views
YYYY-MM-DDTHH:MM:SS.439+0000 ERROR [vcf_dm,67a5548d896d5d28231f671cf7ba47ce,f477] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-7]  Failed to connect to https://esx01.domain.local:443/sdk
com.vmware.vim.vmomi.client.exception.ConnectionException: https://esx01.domain.local:443/sdk invocation failed with "java.net.NoRouteToHostException: No route to host"
       at com.vmware.vcf.configreconciler.config.checks.RemoveNfsDatastoreConfigDriftCheck.lambda$isConfigurationRealized$1(RemoveNfsDatastoreConfigDriftCheck.java:117)
        at org.springframework.retry.support.RetryTemplate.doExecute(RetryTemplate.java:329)
        at org.springframework.retry.support.RetryTemplate.execute(RetryTemplate.java:209)
        at com.vmware.vcf.configreconciler.config.checks.RemoveNfsDatastoreConfigDriftCheck.lambda$isConfigurationRealized$2(RemoveNfsDatastoreConfigDriftCheck.java:114)
        at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)
        at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:59)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.net.NoRouteToHostException: No route to host
..
YYYY-MM-DDTHH:MM:SS.439+0000 DEBUG [vcf_dm,67a5548d896d5d28231f671cf7ba47ce,f477] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-7]  login failed for esx01.domain.local, will retry in 20 seconds!
YYYY-MM-DDTHH:MM:SS.439+0000 DEBUG [vcf_dm,67a5548d896d5d28231f671cf7ba47ce,f477] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-7]  Connecting to https://esx01.domain.local:443/sdk

Environment

VCF 5.x 
SDDC Manager 5.x

Cause

RemoveNfsDatastoreConfigDrift check connects to every host to check for the presence of a datastore that needs to be deleted in this drift. Since it could not connect to the host esx01.domain.local, the drift check failed showing the error.

Resolution

Resolve the host issue causing it to be in 'not responding' state on the vCenter.