In VMware Cloud Foundation (VCF) Orchestrator 9.0.2, you may experience an issue where policy runs hang in a starting state after execution.
search cancel

In VMware Cloud Foundation (VCF) Orchestrator 9.0.2, you may experience an issue where policy runs hang in a starting state after execution.

book

Article ID: 438525

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

After upgrading to VCF Orchestrator 9.0.2 (formerly VMware Aria Orchestrator), you may find that policy runs hang indefinitely in a Starting state. This issue typically occurs when a user or user group is assigned multiple roles, such as Workflow Designer and Viewer. The Orchestrator UI shows the policy as initiated, but it never progresses to an active running state.

Environment

  • Product: VCF Orchestrator / VMware Aria Orchestrator
  • Version: 9.0.2
  • Upgrade Path: Upgraded from Aria Orchestrator 8.x

Cause

Orchestrator defaults to the most restrictive permission assigned to you. If you are assigned both a Workflow Designer role and a Viewer role, the system applies the Viewer restrictions. This limits you to read-only access for certain object-level operations, causing policy executions—which require active rights—to hang during the initialization phase.

Resolution

To resolve this issue, you must remove the overlapping restrictive roles from the affected user or group:

  1. Access the Orchestrator control center or client interface.
  2. Navigate to the permissions or role assignment section for your identity provider groups.
  3. Locate the group or user experiencing the issue.
  4. Review the assigned roles. If both Workflow Designer and Viewer are present, remove the Viewer role.
  5. Confirm that you retain the Workflow Designer role for creation and execution rights, or the Administrator role for full access.
  6. Go in to Polices and open and then save the policies in question and update the description to add a single change to the description.
  7. Save the changes and log out and log back in.
  8. Attempt to run the policy again; it should now transition from Starting to Running successfully.