- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I saw the error that Update Manager no longer works with Active Directory accounts. I'll wait for a fix for that.
I'm also not able to sync updates with the Lifecycle Manager anymore. I updated to 7.0.3 without mishap but when I try to sync updates manually or allow it to happen automatically it gives the error:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try SSHing into hosts while in maintenance mode and running:
esxcli software vib remove --vibname=i40enu
Reboot host.
Then try syncing updates again.
In 7.0.3 VMware had changed the name i40enu back to i40en, some systems get stuck with both versions installed, thus causing a conflict. Removing the old enu version should resolve the conflict.
Obviously, you should confirm installed VIBs\packages and see if both are present before running the above command. This is important if you actually don't have both versions installed and the old package is in use.
VCP-DCV 2021
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'll give it a try, but I'm confused at why the host would have anything to do with the update manager (now lifecycle manager) server not having the right set of software updates or being able to download them correctly from vmware.
I thought lifecycle manager was now embedded into the vcenter server appliance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did that solve Your issue? I have the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seeing this as well.
- vCenter Server is on 7.0.3c (19234570)
- Hosts are on 7.0.2a (17867351)
ESXi 7.0.2a is not affected by the i40en driver conflicts according to https://kb.vmware.com/s/article/86447 so it's probably unrelated.
Update: Seems like this problem is not new. I reverted vCenter back to 7.0.2d (18455184) which didn't fix it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Resetting the Update Manager Database fixed it: https://kb.vmware.com/s/article/2147284