Post upgrade to 7.0 U2, ESXi hosts do not show the vmkernel interfaces

Products

• VMware vSphere ESXi

Issue/Introduction

• Post upgrade to 7.0.2, ESXi hosts do not show the vmkernel interfaces. However, the interfaces are still available can be pinged.
• From the vSphere client, at Host → Configure → VMkernel Adapters Tab "No Items Found" is reported.
• From the ESXi command line, the command 'localcli network ip interface list' or 'esxcfg-vmknic -l', returns the error - 'Unable to get node: Not Found'.
• In hostd.log reports below error:
  
  [YYYY-MM-DDTHH:MM:SS] info hostd[2102849] [Originator@6876 sub=Solo.Vmomi opID=esxcli-##-#### user=####] Result:
--> (vim.EsxCLI.CLIFault) {
--> errMsg = (string) [
--> "Unable to get node: Not found"
--> ],
--> msg = "",
--> }

Note: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 7.0.2

Cause

Post upgrade, one or many vmkernel interfaces may encounter error during the jumpstart phase. This will result in the remaining vmkernel interfaces not being correctly restored.

Resolution

This issue is resolved in VMware vSphere ESXi 7.0 U3d version. To download go to the Support Portal Solution Files page

Workaround:

To workaround this issue follow the below steps.

• Post upgrade, while the host is still in maintenance mode, run the below command to manually update the config-store:

/usr/lib/vmware/sqlite/bin/sqlite3 /etc/vmware/configstore/current-store-1 "UPDATE config SET Success=1 WHERE name='vmknics';"

• Disconnect/reconnect the host to the vCenter.

NOTE :This workaround is not persistent across reboot. Every time the host is rebooted, the above workaround needs to be performed.

Additional Information

Impact/Risks:
None