Workflow or Action Fails with "vcSDK is not defined" after vCenter certificate change
Article ID: 398069
Updated On:
Products
Issue/Introduction
A customer reported a failure while running a post-provisioning workflow in VMware Aria Automation. The error occurred in the action getVirtualCenterSDK, triggered during the Compute post provision phase.
The specific error returned was:
An exception occurred: ReferenceError: "vcSDK" is not defined. (Dynamic Script Module name: getVirtualCenterSDK#14) Running workflow: Compute post provisionThe issue is observed anytime the vCenter certificate has been recently updated. Attempts to rerun the workflow will consistently fail until remediated.
Environment
VMware Aria Automation 8.x
VMware Aria Automation Orchestrator 8.x (embedded or standalone)
VMware vCenter 7.x - 8.x
Cause
The Automation Orchestrator VC plugin failed to re-establish trust with vCenter after a certificate rotation. When the certificate is updated on the vCenter Server, Orchestrator requires the new certificate to be manually imported. Until this trust is re-established, the VC: object references used in actions or workflows (e.g., vcSDK) will return as undefined.
Resolution
To restore VC object references and resolve the script execution error, run the following workflow from VMware Aria Orchestrator:
Workflow Name: Update a vCenter Server instance
Steps:
-
Navigate to Orchestrator Client.
-
Locate the workflow:
Library > vCenter > Configuration > Update a vCenter Server instance -
Run the workflow.
-
When prompted, select the vCenter instance with the updated certificate.
-
Accept the certificate when prompted.
Once completed, re-run the failed workflow. The vcSDK reference should now resolve properly.
Additional Information
This behavior is expected when vCenter's SSL certificate is replaced or renewed and not re-imported into Orchestrator.
For similar symptoms involving VC: object failures, always verify that the certificate trust is intact in Orchestrator.
Feedback
