Post migration from vRA 6.x to vRA 7.x, existing IaaS blueprints are converted to composite blueprints (CBP) with one IaaS item inside.

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Post migration from vRA 6.x to vRA 7.x, provisioning fails when default values are used instead of inputted values for 'Request a Catalog Item' workflows.

Environment

VMware vRealize Automation 7.4.x
VMware vRealize Automation 7.1.x
VMware vRealize Automation 7.2.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 7.0.x

Cause

After upgrading from vRA 6.x to vRA 7.x, existing IaaS blueprints are converted to Composite Blueprints (CBP) with one IaaS item inside.
Composite Blueprints may have many components and each component may have child components as well.

 

As a result of this change:

• The old Blueprint type in the plugin is replaced with vCACCAFECompositeBlueprint.
• Some of the global properties as provider-Cafe.Shim.VirtualMachine.NumberOfInstances and provider-_cluster will have different behavior if they are used on blueprint level.
• Only a part of the parameter provided on blueprint level are passed to the component level

In vRA 7.3 forms for IaaS, related resource operations have been updated to accept dates, numbers and entity references instead of simple strings.
 

 

Resolution

This issue is resolved in VMware vRealize Automation 7.4, available at VMware Downloads.

To resolve this:

1. In vRA 7.0 and 7.0.1, Request a Catalog Item fails, as a workaround use Request a catalog item with provision request .
2. In vRA 7.1 and later, it is possible to specify parameters in the form provider~<component_id>~<parameter_id>, when using a Request a catalog item workflow. 
   
   When there are nested components then it is possible to specify parameters in the form <provider~<component_1_id>~<component_2_id>~<parameter>
3. In vRA 7.3, the Request a resource action with a request template workflow should be used to provide values for dates, numbers and entity references. 
   
   For example:
   
   "arg" : {
   "componentId" : null,
   "classId" : "principal",
   "id" : "[email protected]"
   }