Migrate ESXi Host NFS vmknic(s) to vSphere Distributed Switch", the error states, "Failed to configure Vswitch to DVS vmknic migration on Host <hostname>" as shown in below screenshot:
In the domainmanager.log files, a NullPointerException is logged during the MigrateHostNfsVmknicsToDvsAction workflow stage: java.lang.NullPointerException: Cannot invoke "com.vmware.vim.binding.vim.host.VirtualNic.getSpec()" because "vmknic" is null
/var/log/vmware/vcf/domainmanager/domainmanager.log
YYYY-MM-DDTHH:MIN:SEC##+## INFO [vcf_dm,######,##] [c.v.v.c.f.p.a.i.MigrateHostNfsVmknicsToDvsAction,dm-exec-4] Migrating Host <ESX-fqdn> vmknics to DVS dvs-##YYYY-MM-DDTHH:MIN:SEC##+## INFO [vcf_dm,######,##] [c.v.v.c.f.p.a.i.MigrateHostNfsVmknicsToDvsAction,dm-exec-4] Migrating vmknic 10.0.0.0 on host <ESX-fqdn> to dvs dvs-## portgroup dvportgroup-##YYYY-MM-DDTHH:MIN:SEC##+## INFO [vcf_dm,######,##] [c.v.v.c.f.p.a.i.MigrateHostNfsVmknicsToDvsAction,dm-exec-4] Is DHCP enabled on this environment falseYYYY-MM-DDTHH:MIN:SEC##+## DEBUG [vcf_dm,######,##] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Getting entity type VmwareDistributedVirtualSwitch with moid dvs-## from vcenterYYYY-MM-DDTHH:MIN:SEC##+## DEBUG [vcf_dm,######,##] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Retrieved MoRef: {"_type":"VmwareDistributedVirtualSwitch","_value":"dvs-##"}YYYY-MM-DDTHH:MIN:SEC##+## INFO [vcf_dm,######,##] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Migrating NFS Vmknic To DvSwitch 10.0.0.0YYYY-MM-DDTHH:MIN:SEC##+## DEBUG [vcf_dm,######,##] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Finding host with fqdn <ESX-shortname>.us.cambridgeYYYY-MM-DDTHH:MIN:SEC##+## ERROR [vcf_dm,######,##] [c.v.v.c.f.p.a.i.MigrateHostNfsVmknicsToDvsAction,dm-exec-4] Failed to migrate Host Vmknic to DVS for host <ESX-fqdn>java.lang.NullPointerException: Cannot invoke "com.vmware.vim.binding.vim.host.VirtualNic.getSpec()" because "vmknic" is null
VMware Cloud Foundation 9.x
VCF 9.x
When deploying VMware Cloud Foundation (VCF) with useExistingDeployment: true, the VCF Installer VM runs directly on an ESXi host that participates in the bringup workflow and is hosted on a preconfigured NFS datastore. If the VMkernel adapter (vmknic) pre-created for NFS on that host is assigned an IP address that is not the first address in the defined NFS IP range, the bringup workflow skips vmknic creation on that host. Consequently, subsequent hosts in the cluster receive IP assignments offset from what the migration logic expects, causing the vSwitch to vSphere Distributed Switch (DVS) migration task to fail.
To resolve this deployment failure, you must manually align the host's network configuration with the parameters expected by the VCF bringup workflow. This is a known issue and has been fixed in VCF 9.1.
Follow below mentioned workaround steps to unblock VCF deployment if an upgrade/deployment to version 9.1 isn’t feasible.