Assembler. Making an image mapping available to multiple regions fails.

[Michael Cornn]

In vCenter, we have two datacenters named Colo and Davis. If we make two separate image mappings, each available to one region, deployments work properly. If we make one image mapping, available to both regions, deployments fail. 

In the screenshot below, there is an image mapping named "Server 2022 Template". It has two entries, for datacenters 'Colo' and 'Davis'.

The YAML for our Assembler template has a constraint of "c1" or "d1". This constraint tag is applied to some compute resources, but it is not applied to any image mappings. 

formatVersion: 1
inputs:
  dataCenter:
    type: string
    title: Data Center
    description: Data Center in which to deploy the VM.
    enum:
      - c1
      - d1
resources:
  Windows Server:
    type: Cloud.vSphere.Machine
    properties:
      image: Server 2022 Template
      name: 'MyPC'
      cpuCount: 1
      totalMemoryMB: 1024
      constraints:
        - tag: ${input.dataCenter}

When we select 'd1' as the constraint, a test works properly. 

When we select 'c1' as the constraint, the test fails with  the error 'Cannot find matching image mappings for image: Server 2022 Template" 

The provisioning diagram for the test produces a very odd error: "Could not match: Server 2022 Template. Close match Server 2022 Template"

What could possibly cause this error?

-------------------------------------------

[Shen88]

@Michael Corn,

We might have to validate a few things before jumping into resolution, as the reason for such error could vary.

The error implies that while a template with a similar name exists, it does not meet the specific conditions or constraints defined in the provisioning diagram, 

Maybe the "Server 2022 Template" has not been assigned the correct constraint tags (e.g., region, environment, or datacenter tags) required by the blueprint.

The template might be available in one region/datacenter but not the one specified in the current provisioning request.

 A simple typo in the template name or the constraint tag within the provisioning diagram could cause the mismatch. The error message "Close match Server 2022 Template" reinforces this possibility.

Sometimes, after making changes to image mappings or tags, the system's cache may not update immediately.

Please validate these and also share the vRA version you have.

------------------------------
If you find this answer right, please 'Recommend' this post.

Thank you!

Regards,
Shen
------------------------------