VMware Cloud Community
Eudmin
Enthusiast
Enthusiast
Jump to solution

7.0.3 Update manager won't sync updates

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:

 A general system error occurred: com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError
 
Any tips on how to fix it?  It was working with 7.0.2 Update d as far as I know.
1 Solution

Accepted Solutions
sysadmin84
Enthusiast
Enthusiast
Jump to solution

Resetting the Update Manager Database fixed it: https://kb.vmware.com/s/article/2147284

View solution in original post

0 Kudos
5 Replies
DanMc85
Enthusiast
Enthusiast
Jump to solution

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.

- DanMc85
VCP-DCV 2021
0 Kudos
Eudmin
Enthusiast
Enthusiast
Jump to solution

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.

0 Kudos
deniswer
Contributor
Contributor
Jump to solution

Did that solve Your issue? I have the same.

0 Kudos
sysadmin84
Enthusiast
Enthusiast
Jump to solution

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.

0 Kudos
sysadmin84
Enthusiast
Enthusiast
Jump to solution

Resetting the Update Manager Database fixed it: https://kb.vmware.com/s/article/2147284

0 Kudos