Vijay2027's Posts

Adding on to what @baijup said, I've seen HA related issues post patching and below is one of the scenario where fdm failed to install due to dependency error. You can see the list of conflicting VIB's in /var/run/log/esxupdate.log or simply by running the following command [root@esxi1:~] esxcli software vib remove -n vmware-fdm --dry-run  [DependencyError]  VIB QLC_bootbank_qedi_2.19.51.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.40.28.0, but the requirement cannot be satisfied within the ImageProfile.  VIB QLC_bootbank_qedrntv_3.11.33.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.40.28.0, but the requirement cannot be satisfied within the ImageProfile.  VIB QLC_bootbank_qedentv-ens_3.11.33.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.40.28.0, but the requirement cannot be satisfied within the ImageProfile.  VIB QLC_bootbank_qedf_2.2.52.1-1OEM.670.0.0.8169922 requires qedentv_ver = X.40.28.0, but the requirement cannot be satisfied within the ImageProfile.  Please refer to the log file for more details. Place host in MM and run the following command to remove VIB's # esxcli softwrae vib remove -n qedi -n qedrntv -n qedentv-ens -n qedf Reboot and reconfigure for vSphere HA from H5 client.

When placing the hosts in MM do you see the following error in wcpsvc.log: "Error occured looking for solution user :: More than one solution user found :: More than one solution user found" Please run the following command on all vCenter servers in SSO domain and share output: /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store wcp --text | grep -i "Subject:"