Post-deployment Orchestrator workflow scripts not executing and producing vim3WaitToolsStarted error

Products

• VMware Aria Suite

Issue/Introduction

Orchestrator workflows that run after a new deployment is created (set admin/root password, adjust network, set hostname, ..) show as "Completed".

These workflows push respective PowerShell/bash scripts to the designated VMs, however the scripts are not being executed, and users are unable to log in with the new passwords.

The workflow logs all have the following error:

ERROR (com.vmware.library.vc.vm.tools/vim3WaitToolsStarted) Error in (Dynamic Script Module name : vim3WaitToolsStarted#1) ReferenceError: vm is not defined for waiting for the DNS name

Environment

Aria Automation 8.18.1

Orchestrator VC Plug-in 8.1.1.24147893

Cause

The issue is due to regressions in the VMware vCenter (VC) plugin 8.1.1.24147893.

Resolution

This is a known issue with the Orchestrator VC Plug-in 8.1.1.24147893 on Aria Automation 8.18.1.

The fix is to downgrade the plugin to the attached version (o11n-plugin-vsphere-8.1.1+24070852.vmoapp).

Workaround :

Before proceeding, we highly recommend taking a non-memory snapshot of vRA/vRO.

1. Download the attached plug-in file to your local machine.
2. In Automation Orchestrator, select System Settings.
3. On the Plug-ins card, click Open.
4. Click Add Plug-in.
5. In the General pane, click Select and add the plug-in file.
6. Select a log level.
7. Click Next.
8. Review the plug-in information, if applicable, accept the end-user license agreement, and click Install.
9. Click Upload.

After the plugin is installed, the Automation Orchestrator server service will be restarted.

Additional Information

NOTE: You may observe VC plugin warning in the event one already exists. 

In that case, remove the existing plugin VC 8.1.1.24147893 before installing the attached version.