I'm seeing older version of OpenManage that had this same error and it was a bug.
Things I have done: Reinitialize VUM database, which I can then scan the hosts successfully. Once I add back in the Dell repo, it starts failing again with the above error in the esxupdate.log file.
The last I heard from Dell, they said they weren't going to fix this but focus on the next release. I haven't seen an 8.4 release, so as a work around, you'll have to uninstall OMSA 8.3 from all of your machines and then install it again from the repo.
Huge PITA though. Other option is to reset your vCenter VUM database and don't add back in the Dell repo. Then you'll be able to scan your hosts w/o issue again.
I verified the issue. I compared the cross_dell-openmanage-esxi_8.3.0.ESXi600-0000.vib file from the Dell repo and then the one that comes inside of the zip file on the download page.... they are different sizes.
I've had a ticket open with Dell for this issue and they told me they are NOT going to release an incremental version to fix this issue, they are just going to focus on the next release.
Manually running an uninstall on 100+ hosts isn't an option.
What I did to fix my issue was resetting the VUM database and not putting the dell repo back in. That allowed Update Manager to successfully scan again.
When the new version comes out, i'll add it back in to upgrade all of my hosts.
OneLoveAmaru14
8 Posts
2420
1
Posted September 11th, 2016 17:00
The last I heard from Dell, they said they weren't going to fix this but focus on the next release. I haven't seen an 8.4 release, so as a work around, you'll have to uninstall OMSA 8.3 from all of your machines and then install it again from the repo.
Huge PITA though. Other option is to reset your vCenter VUM database and don't add back in the Dell repo. Then you'll be able to scan your hosts w/o issue again.
Thanks Dell!!!