Cloud Zone based Virtual Machine constraints are ignored when placement is being determined.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When deploying a Virtual Machine where you have defined constraints based on cloud zones, the constraints are ignored and placement occurs randomly.

Environment

Aria Automation 8.x

Cause

This can be caused by improper placement of the tag constraint within the blueprint.  Blueprint validation does not catch this issue because it passes syntax validation but the constraint is ignored when placement is determined.

Resolution

Validate that your constraint is nested under the properties subsection and not under the virtual machine itself.

Incorrect Example where constraint is nested under the machine but at the same level as properties:

  Cloud_Volume_1:
    type: Cloud.Volume
     constraints:
       - tag: placement:myzone1 
     properties:
      name: ${input.disk-name}
      capacityGb: 1

Correct Example where the constraint is nested under the properties section:

  Cloud_Volume_1:
    type: Cloud.Volume
    properties:
      name: ${input.disk-name}
      capacityGb: 1
      constraints:
        - tag: placement:myzone1