book
Article ID: 337045
calendar_today
Updated On:
Issue/Introduction
To simplify the image mappings and reduce the time taken to provision a virtual machine.
Symptoms:
- After upgrading to vRealize Automation 8.3, creating a new image mapping, subscriber templates will not be visible. Only publisher templates are now visible.
Environment
VMware vRealize Automation 8.3.x
Cause
There was a feature in vRealize Automation 8.3 that specified this new behavior. With image mapping trimmed down to just publisher templates, vRealize Automation at run time finds the subscriber template local to the vCenter where the machine will be provisioned. So speed of deployment will not be compromised.
Resolution
This is an expected behavior
For more information, see:
Note: For vRealize Automation version 8.4.1 onwards, the actual template used for cloning the Virtual Machine is now shown in the machine details in the Deployments UI.