Skip to main content

Reason for recalling VMWare vSphere 7.0 U3 Version

VMware just recalled their latest update for vSphere and vCenter Server 7.0 U3b is no longer available for download. If your vCenter has already been upgraded to vCenter 7.0 U3b\and is experiencing the symptoms mentioned in KB 86191, please remove the i40enu driver.
Issues
  • After patching ESXi to 7.0 Update 3 - HA can no longer be successfully enabled
  • When trying to enable HA, the installation of the HA agent (FDM) starts, and the status switches into "Waiting for cluster election to complete", only to fail and start over again
  • The HA status for the ESXi host is stuck at "Uninitialized"
  • In some cases the HA enablement task fails with "Cannot find vSphere HA master agent"
  • Migrating or powering on VMs in an HA enabled cluster fail
  • In /var/run/log/esxupdate.log on the ESXi, you find the following entries:
esxupdate.log
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR: Traceback (most recent call last):
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 773, in <module>
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     main()
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 764, in main
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     ret = CMDTABLE[command](options)
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 601, in VibInstallCmd
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     res = t.InstallVibsFromSources(viburls, [], nameids,
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 965, in InstallVibsFromSources
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     inst, removed, exitstate = self._installVibs(curprofile,
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 1207, in _installVibs
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     hasConfigDowngrade = checkFdmConfigDowngrade(curProfile, newProfile)
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/lib64/python3.8/site-packages/vmware/esximage/Transaction.py", line 1122, in checkFdmConfigDowngrade
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     compDowngrades = curProfile.GetCompsDowngradeInfo(newProfile)
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/lib64/python3.8/site-packages/vmware/esximage/ImageProfile.py", line 2416, in GetCompsDowngradeInfo
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     curComp = self.components.GetComponent(name)
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:   File "/lib64/python3.8/site-packages/vmware/esximage/Bulletin.py", line 1276, in GetComponent
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR:     raise ValueError('Expected 1 component, found %u'
2021-10-13T14:01:17Z esxupdate: 2140874: root: ERROR: ValueError: Expected 1 component, found 2
Cause
  • This issue occurs when both the i40en and i40enu VIBs for the inbox Intel network driver are installed on the host
  • The issue was also reported after upgrading to vCenter 7.0 Update 3b, released on 12th November 2021, which is no longer available.
  • In vSphere 7.0 Update 2, the driver was renamed from i40en to i40enu. Starting with vSphere 7.0 Update 3, the inbox i40enu network driver for ESXi changes back to i40en
Resolution
This issue will be resolved in an upcoming release of VMware ESXi.
The issue was also resolved in VMware ESXi 7.0 U3b build 18905247 (No longer available)
Note:- vSphere ESXi 7.0 U3, U3a, and U3b and vCenter 7.0 U3b are no longer available for download due to several critical issues identified in them. For information regarding this decision, Please refer to KB 86398 
Temporary Solution
To work around the issue, remove the conflicting i40enu driver
  1. Disable vSphere HA on the cluster with the affected hosts.
  2. Put the ESXi in maintenance mode, then run the following command to remove the obsolete i40enu VIB :
esxcli software vib remove --vibname=i40enu
  1. Once the VIB has been removed, reboot the ESXi host.
  2. When this has been done for all hosts in the cluster, HA can be enabled again.
Labels:

Comments

Post a Comment

Popular posts from this blog

INTRODUCTION TO NETWORK SIMULATOR 2

  INTRODUCTION  Network Simulator Version 2, widely known as NS2, is an event driven simulation tool that is useful in studying the dynamic nature of communication networks. Simulation of wired as well as wireless network functions and protocols (e.g., routing algorithms, TCP, UDP) can be done using NS2. In general, NS2 provides users with a way of specifying such network protocols and simulating their corresponding behaviors. Due to its flexibility and modular nature, NS2 has gained constant popularity in the networking research community since its birth in 1989. Ever since, several revolutions and revisions have marked the growing maturity of the tool, thanks to substantial contributions from the players in the field. Among these are the University of California and Cornell University who developed the REAL network simulator,1 the foundation which NS is based on. Since 1995 the Defense Advanced Research Projects Agency (DARPA) supported development of NS through the Virtual ...
Post a Comment
Read more

Matter: A next generation home standard

The smart home is evolving. To date, if you've wanted to get into developing a smart home, you've had to deal with the multitude of smart home ecosystems, and making sure that each device you buy is compatible. That, however, may soon change — thanks to new smart home standard called Matter. Matter isn't available just yet, but when it is finally released, it could completely change how you buy smart home products, for the better. All of the best smart home devices could soon support the standard, helping them all work together nicely, and ensuring that no matter what products you buy, you'll be able to use them. Matter is basically the name of a new smart home connectivity standard . But this standard is a little unlike others. That's because of the fact that it's being developed by the Connectivity Standards Alliance, which counts hundreds of companies as members. That includes the likes of Google, Alexa, and Apple. So, whether you prefer to use Google Assista...
1 comment
Read more

How to turn off package notifications on Alexa

Echo smart speakers and smart displays have a handy feature that can show and tell you when there’s a package sitting on your doorstep and even what’s in it. While this can be helpful most of the time, around the holidays it could seriously ruin some surprises. Avoid making any Grinch-like moves this holiday and manage your Amazon shopping notifications in the Alexa app to help keep the magic alive. Alongside options for tailoring package announcements, the notifications section of the app also has a number of settings you can toggle on or off to help make the voice assistant a little more helpful when it comes to purchases you make on Amazon. Below are a few of the most useful that you might want to tweak this holiday season. Open the Alexa app. Tap on More in the bottom right hand corner. Select Settings > Notifications > Amazon Shopping . Under “Say or Show Item Titles” toggle off “including items in your shopping cart marked as gifts, or those that might be gifts during major...
Post a Comment
Read more