During the last weekend, I took the time to start with some home lab upgrades. I wanted to start checking all the new vSphere 6.5 goodies and some of the cool new Windows Server 2016 features, Docker integration being one of them. The new integrated Update Manager is finally here and but unfortunately, my first interaction with it was around VIB conflict.
I have nice lab consists of 3 Whitebox hosts (two types of those) for management cluster and a couple of Dell OptiPlex 790 SFF hosts for payload and other automation related tests. All are installed with ESXi 6.0 and connected to couple vCenter Server 6.0 appliance.
For the upgrade, I’ve started with deploying the new vCenter Server 6.5 appliance (very slick deployment BTW) followed by the first Whitebox host. I’ve uploaded the ESXi 6.5 image to update manager, created a baseline, attached it to the host and started the remediation process. Right of the back VUM told I have a VIB conflict. To be completely honest I am not sure where this OEM_bootbank_OEM-00_1.0 is coming from.
A simple esxcli software vib list | grep “OEM” command showed me the bad vib which also makes you wonder why VUM reporting two vib’s conflict, possibly this is a UI bug.
The only thing left to do is to remove it. Another esxcli software vib remove –vibname OEM-00 command and then performing host reboot.
Once I got back to VUM the host was in a Non-Compliant state as it should be.
After that, I was able to remediate to host and complete the upgrade successfully.