Action fails with OOM error during workflow

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When running a workflow, such as "Compute post provision," the process fails. In the vRealize Orchestrator (vRO) UI or logs, you see an error message similar to the following:

Wrapped ch.dunes.scripting.server.polyglot.PolyglotRunnerException: Function was stopped. Most likely because it hit an OOM (out of memory) condition. Container memory config: 500000000

This error indicates that a specific vRO action (e.g., deriveFolderNameFromTag) ran out of memory. The message Container memory config: 500000000 shows the action was limited to 500MB of memory when it failed.

 

 

Environment

Aria Automation/Orchestrator 8.18.x

Cause

The vRO action being executed requires more memory than its currently configured limit. The default or previously set memory (e.g., 500MB) is insufficient for the action to complete its task, causing the container to be terminated with an Out Of Memory (OOM) error.

Resolution

You must increase the memory allocation for the specific vRO action that is failing.

1. In the vRO client, navigate to the Actions tab.

2. Locate and select the failing action

3. Edit the action's configuration settings.

4. Find the Memory Limit setting.

5. Increase the value to an appropriate amount. In this case, increasing the limit from 500MB to 600MB resolved the issue.

6. Save the action's new configuration.

7. Run the workflow again to confirm the issue is resolved.