BugZero | VMware vCenter BugID 3537457 - You cannot create VM Storage Policy for tag-based ...

VMware vCenter - Defect ID: 3537457

You cannot create VM Storage Policy for tag-based placement using tag-category and tags created by REST API calls

VMware vCenter - Defect ID: 3537457

You cannot create VM Storage Policy for tag-based placement using tag-category and tags created by REST API calls

Last updated on May 7th, 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: Storage Issues
Workaround Available:

Description

Disclaimer

Known affected version(s) that were inferred because the vendor did not provide any: 8.0.3.00600

Overview

When you create a tag for a VM Storage Policy for tag-based placement by using vMODL2 REST API calls, a tag category is successfully created, but tags of this category do not show as available options when configuring a new tag-based storage policy. This issue is resolved in this release.

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-80u3h-release-notes.html

Change history

2025-12-22 changed to Resolved

Top VMware vCenter Defects

Defect ID: 3602673
Tasks for cloning and export to a content library might fail if you restrict network packets that use plain text
Defect ID: 3488172
Login instructions for RSA SecurID Authentication in the vSphere Client might display HTML tags as plain text
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

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: 3537457

You cannot create VM Storage Policy for tag-based placement using tag-category and tags created by REST API calls

VMware vCenter - Defect ID: 3537457

You cannot create VM Storage Policy for tag-based placement using tag-category and tags created by REST API calls

Last updated on May 7th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Disclaimer

Overview

Bug URLs

Links

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
0.0 Coming soon