When deploying a VM via a template that has a storage constraint, the placement is landing on the wrong storage profile

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• One storage profile has both tags and another has one of the tags, but the VM is getting placed on the profile that only has one tag and is the default for the region. 
  Note: the following are examples and the tag names and the number of tags will vary for each environment.
  
  
• The cloud template contains constraints similar to the following:
  
       constraints:
          - tag: type:tier2
          - tag: env:dev
• Storage profiles may have 2 tags each, but when viewing the Provisioning Diagram for the deployment, it shows more tags matching on the Storage Profile that should not match.
• In this example the desired Profile is Profile 2, but Profile 1 is selected:
  
• If you view the Storage profiles, they have the correct tags:
• Opening the Datastores in the Profile shows that tags have been applied that match the cloud template constraints:
  

Environment

Aria Automation 8.x

Cause

There are tags configured on the datastores that match the Cloud Template

Resolution

1. Remove the Tags from the Datastores or use tags that are unique to the Storage Profiles to allow for the selection to be made by the Storage profile.
   
   
2. Test the deployment and view the Provisioning Diagram

Result after removing the tags from the datastores: