Was going to try to upgrade the first host in a vSAN cluster from 6.7 to 7.0 (Using Custom Dell Image) but upon attaching upgrade baseline and run Check Compliance it showed Status "Incompatible"
The upgrade has VIBs that are missing dependencies:
Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again.
esxcli software vib list | grep 126.96.36.199-1OEM.5188.8.131.521820
net-qlge 184.108.40.206-1OEM.5220.127.116.111820 QLogic VMwareCertified 2019-03-16
By removing the VIB's does it mean login to ESXi and remove the the above VIB such as by doing following command?
esxcli software vib remove -n net-qlge
Why is this an issue and more important will removing the above VIB cause any issue as presumably since it is listed it is in use?
Although I can not see net-qlge listed under Driver when doing esxcli network nic list or esxcli storage core adapter list
Such dependency errors have been around for quite some time. Anyway, since you've already verified that the mentioned drivers are not in use, there should be no issues with removing them using the command that you've mentioned.
ok so net-qlge is just loaded but not in use as otherwise it would show under "Drivers"
In which case I will esxcli software vib remove -n net-qlge
Then will check Compliance Status again and push the upgrade.
ok following the above and rebooting Status showed as Non Compliant
Remediated and upgrade completed however in Events I could see message "vSAN network is not configured" after it completed!
I checked the vmkernel and in fact vSAN Service is unticked (otherwise rest of settings (IP/MTU) on vmkernel look to have persisted)
Is this known or any reason why this would happen and any further checks you suggest me doing as at this point it might have missed other config?
thank you, in my case the vib listed was not in used so I could remove it prior the ESXi upgrade.
The strange thing is that vSAN is getting ticked off from the vSAN dedicated vmkernel after the upgrade, it must be a bug as the same happened with 2nd host upgrade.