Just fixed this issue. We had to re-register the update manager extension and change ownership of the integrity xml file as it loses its permissions and defaults to root/root.
1. Take a snapshot
2. SSH to the VCSA(Version 126.96.36.199000)
3. Run the following to re-register the extension:
/usr/lib/vmware-updatemgr/bin/vmware-vciInstallUtils -C /usr/lib/vmware-updatemgr/bin/ -L /var/log/vmware/vmware-updatemgr/ -I /usr/lib/vmware-updatemgr/bin/ -v YOURVCSAFQDN -p 80 -U firstname.lastname@example.org -P 'REALPASSWORDHERE' -S /usr/lib/vmware-updatemgr/bin/extension.xml -O extupdate
4. The file vci-integrity.xml only has root user permissions. Give ownership to updatemgr.
chown updatemgr:updatemgr vci-integrity.xml
5. Restart the update manager service.
We, or the support from VMware, tried all of the above fixes to no avail. Through some testing with the help of vMotion, I figured out that it was being caused by one of the virtual machines. VMware claims that the issue was that the following lines were missing from the vmx file:
tools.upgrade.policy = "manual"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
tools.guest.desktop.autolock = "FALSE"
The only "tool" related line in our vmx file was:
tools.syncTime = "FALSE"
After recreating the virtual machine the issue went away. However, the above configuration lines are still missing and it's not causing a problem. VMware was eager to close the ticket, but I think the underlying bug still remains.
Well it worked for a short while, the issue is back. How do you identify the one vm with the missing vmx info? This is affecting the whole vcenter.
We have three ESXi hosts, and while the issue is present at the cluster level, it was only present on one of the three hosts. By vMotioning VMs I discovered that the issue went moved between hosts. With some more vMotioning between the hosts, I narrowed it down to a single VM.
I have the same error - An unexpected error has occurred. 3 hosts. 6 VMs. Version - 188.8.131.52000
Had the same issue with all VMs, but restarting the Update Manager service on the VCSA worked for me. We recently had to free up space on the SEAT partition which was getting full, so maybe this had caused it to stop functioning properly until the service was restarted.
to confirm i have the same symptoms using SRM 8.1.2 with VCSA 6.7 U3
i have an open support ticket with vmware so will provide more info once i get an update.
Thank you, this worked for me.
a curiosity, have you tried to perform a "Storage vmotion"?
I would do this test if it is possible: rename the VM, do a "Storage vMotion". Then rename it to the old name and run "Storage vMotion" on the previous host again. It's a little cumbersome but it could fix things.