Built-in resource mappings and mappings based on workflows fail
search cancel

Built-in resource mappings and mappings based on workflows fail

book

Article ID: 336966

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
Invoking a XaaS day 2 operation on a resource fails with an error similar to:
Failed to convert external resource Map to VC:VM. Workflow 'Can not retrieve status.' failed with status {2}.

Environment

VMware vRealize Automation 7.6.x

Cause

Known issue with workflow-based resource mappings

Resolution

If the resource mapping that fails is a built-in resource mapping, apply the steps below to update the database:

  1. Make a backup of the database
  2. Connect to the database
  3. Open a new transaction:
BEGIN;
 
  1. Update the records to have the appropriate action ids assigned:
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCVM' where mappingworkflowid='425bcb81-####-####-####-########732';
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCloudVApp' where mappingworkflowid='4310f443-####-####-####-########624';
UPDATE asd_resourcetype set mappingscriptactionfqn='com.vmware.vcac.asd.mappings/mapToVCloudVM' where mappingworkflowid='c8324dc1-8####-####-####-########a63';

 
  1. Check for errors and commit or rollback.
    1. If there are errors, abort the transaction 
ROLLBACK;
    1. If no errors, commit the transaction:
COMMIT;


If the resource mapping is a custom resource mapping, wrap the workflow it invokes as an action and call the action instead.