mbartle
Enthusiast
Enthusiast

Lifecycle Manager wants to remove a VIB that is used by HA

I have an issue that i'm not sure if this is normal or not.  We are running ESXi 7.0.1 U1d that we upgraded from 6.7 using the traditional ISO / baseline.

I am wanting to bring these up to 7.0.2 U2c using the new image based method.  When i start the process and select the image profile plus the Dell EMC addons, I get this message at the top :

Identified standalone vib(s) vmware-fdm 7.0.2-18356314 belonging to vSphere FDM 7.0.2-18355786 solution component.

When I save and have it validate the image against the HCL, it comes back with :

The following VIBs on the host are missing from the image and will be removed from the host during remediation: vmware-fdm(7.0.2-18356314).

This VIB seems to be the HA agent.  If it removes it during the remediation, will it re-install it again when the host exits maintenance mode ? How else will it be able to be a cluster member ?

 

Screen Shot 2021-09-10 at 11.16.06 AM.png

2 Replies
DavoudTeimouri
Virtuoso
Virtuoso

FDM Agent will be installed by vCenter, so I think that you should test and try it on one of hosts for sure, before upgrading whole cluster.

** If you found this note/reply useful, please consider awarding points for "Correct" or "Helpful" ** Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
0 Kudos
Srijithk
Enthusiast
Enthusiast

you may proceed with it

vcenter pushes an FDM vib once the host exits maintenance mode and then HA gets reconfigured 

if you are facing any issues take an ssh session to host and confirm that fdm isn't installed already

esxcli software vib list |grep fdm

if it isn't refer --> https://kb.vmware.com/s/article/2011688 to get the fdm installed manually

Thanks,

Srijith