vCenter Tag Cardinality is not respected when assigning tags from Aria Automation day2 actions

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

A tag category in vCenter has Cardinality = "single" or in other words, "Tags per object" = "One tag"

When adding VM tags via either the "Manage tags" or "Update tags" day 2 actions on an Automation deployment, an extra tag is nonetheless applied to the VM in vCenter.

Environment

VMware Aria Automation 8.x

VMware vSphere 8.0.3, patch a-h

VMware vSphere 9.0

Cause

Aria Automation uses the /api/cis/tagging/tag-association?action=attach-multiple-tags-to-object  API call which has a known issue, in which one tag is applied to the VM even when the call fails with VapiStdLocalizableMessage (cis.tagging.attach.invalidArgument.cardinality.error)

Resolution

This issue is resolved in vSphere 9.1 and a fix is planned for vSphere 8.0.3i