Loading...
Loading...
Known affected version(s) that were inferred because the vendor did not provide any: 8.0.3.00400
After an upgrade from vCenter 7.x to 8.0 Update 3, while modifying database tables to align with the vCenter 8.x database schema, the CNS.VOLUME_INFO table schema in the CNS.VPX_TABLE might be incorrect. Inserting data into the CNS.VOLUME_INFO table fails with the following error in /var/log/vmware/vsan-health/vsanvcmgmtd.log on vCenter: DB Error while inserting volume ***: Column ALLOCATED_SPACE does not exist in Table Definition of table volume_info" or "Cannot process vStorage objectxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx on ds:///vmfs/volumes/**** . As a result, creating PODs is blocked in ContainerCreating state and Persistent Volumes fail to attach to the nodes. This issue is resolved in this release.
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u3e-release-notes.html
Click on a version to see all relevant bugs
VMware vCenter Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.