BugZero | VMware vCenter BugID 3262556 - vCenter upgrade fails with "VP last sync time not ...

VMware vCenter - Defect ID: 3262556

vCenter upgrade fails with "VP last sync time not updated after waiting for 5 minutes after vCenter update"

VMware vCenter - Defect ID: 3262556

vCenter upgrade fails with "VP last sync time not updated after waiting for 5 minutes after vCenter update"

Last updated on January 19th, 2026

BugZero Risk Score
0.0 Coming soon

Overall: N/A

Severity: N/A

Community: N/A

Lifecycle: N/A

What is the BugZero Risk Score?

VMware vCenter Integration

Learn more about where this data comes from

VMware vCenter Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Status: Known
Impact Category: vCenter Server and vSphere Client Issues
Workaround Available:

Description

Overview

In rare cases, during a vCenter upgrade, a race condition between vSphere API for Storage Awareness (VASA) providers might cause the upgrade to fail. In the pod-service.log file, you see an error such as vSAN VP last sync time not updated after waiting for 5 minutes after vCenter update . This issue is resolved in this release. The fix prevents the race condition.

Bug URLs

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-70u3v-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3q-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3r-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3s-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3u-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3w-release-notes.html

Change history

2025-12-22 changed to Known

Top VMware vCenter Defects

Defect ID: 1c85aec6fb3f
VMware NSX installation or upgrade in a vSphere environment with DPUs might fail with a connectivity error
Defect ID: 3532388
In the vSphere Client, you cannot set the datetime format in Browser Default
Defect ID: 7d43a1f7e479
If you do not reboot an ESXi host after you enable or disable SR-IOV with the icen driver, when you configure a transport node in ENS Interrupt mode on that host, some virtual machines might not get DHCP addresses
Defect ID: d7c9886ee562
Pensando DPUs do not support Link Layer Discovery Protocol (LLDP) on physical switch ports of ESXi hosts
Defect ID: 627ee642d90e
You cannot create snapshots of virtual machines due to an error in the Content Based Read Cache (CBRC) that a digest operation has failed

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: 3262556

vCenter upgrade fails with "VP last sync time not updated after waiting for 5 minutes after vCenter update"

VMware vCenter - Defect ID: 3262556

vCenter upgrade fails with "VP last sync time not updated after waiting for 5 minutes after vCenter update"

Last updated on January 19th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Overview

Bug URLs

Links

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
0.0 Coming soon