BugZero | VMware vCenter BugID 7c68aa1cf7aa - The Utilization view of resource pools and cluster...

VMware vCenter - Defect ID: 7c68aa1cf7aa

The Utilization view of resource pools and clusters might not automatically refresh when you change the object

VMware vCenter - Defect ID: 7c68aa1cf7aa

The Utilization view of resource pools and clusters might not automatically refresh when you change the object

Last updated on May 29th, 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: Resolved
Impact Category: vCenter Server and vSphere Client Issues
Workaround Available:

Description

Disclaimer

A custom bug ID has been generated as the vendor did not provide one: 7c68aa1cf7aa

Overview

When you have already opened the Utilization view under the Monitor tab for a resource pool or a cluster and then you change the resource pool or cluster, the view might not automatically refresh. For example, when you open the Utilization view of one cluster and then select a different cluster, you might still see the statistics of the first cluster.

Workaround

Click the refresh icon.

Bug URLs

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-801-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-802-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80a-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80b-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80c-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1a-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1b-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1c-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1d-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u1e-release-notes.html https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vmware-vsphere-80-release-notes.html

Change history

2025-11-05 changed to Resolved

Relevant Products

Click on a version to see all relevant bugs

Affected versions:8.0.0.10000, 8.0.0.10100, 8.0.0.10200, 8.0.0.10300, 8.0.1.00000, 8.0.1.00100, 8.0.1.00200, 8.0.1.00300, 8.0.1.00400, 8.0.1.00500

Fixed versions: 8.0.2.00000

Relevant Products

Click on a version to see all relevant bugs

Affected versions:8.0.0.10000, 8.0.0.10100, 8.0.0.10200, 8.0.0.10300, 8.0.1.00000, 8.0.1.00100, 8.0.1.00200, 8.0.1.00300, 8.0.1.00400, 8.0.1.00500

Fixed versions: 8.0.2.00000

Top VMware vCenter Defects

Defect ID: 3484244
A rare race condition might cause repeating failovers due to a failure of the vCenter vpxd service or vSphere Client becoming unresponsive
Defect ID: 68adfd8f5272
vSphere Storage vMotion operations might fail in a vSAN environment due to an unauthenticated session of the Network File Copy (NFC) manager
Defect ID: 524f315fc61b
You see large threadmonitor<num>.log files in the vsphere-ui logs directory
Defect ID: bbd459dcb4af
You cannot customize a Linux virtual machine with installed SUSE Linux Enterprise Server 16 (SLES 16)
Defect ID: bcc42dddb81d
Firmware compliance details are missing from a vSphere Lifecycle Manager image compliance report for an ESXi standalone host

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: 7c68aa1cf7aa

The Utilization view of resource pools and clusters might not automatically refresh when you change the object

VMware vCenter - Defect ID: 7c68aa1cf7aa

The Utilization view of resource pools and clusters might not automatically refresh when you change the object

Last updated on May 29th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Disclaimer

Overview

Workaround

Bug URLs

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

Links

BugZero Risk Score
0.0 Coming soon