Error 204 when trying to delete a custom workflow via the VMware Aria Automation Orchestrator API
search cancel

Error 204 when trying to delete a custom workflow via the VMware Aria Automation Orchestrator API

book

Article ID: 326004

calendar_today

Updated On: 03-04-2025

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • When trying to delete a custom workflow or action from the UI no error is produced, the operations simply does not result in a deleted action/workflow.
  • When trying to delete via the API you receive the code 204 undocumented response.

image.png


Environment

VMware vRealize Orchestrator 8.x

Cause

This issue is most commonly caused when a package is created with only the 'v' allow operation.

Resolution

Prerequisites

  • Please take simultaneous non-memory snapshots of each virtual appliance(s) in the cluster.
    • Use the quiesce option for versions 8.9.x and above.
  • You have SSH access with root user and password.

Procedure

  1. SSH to the appliance using the root user account.
  2. Run the following command to connect to the vco-db
vracli dev psql vco-db
  1. Verify the workflow(s) that has the 'v' flag by running this query:
SELECT id,name FROM vmo_workflow WHERE allowedoperations = 'v';
  1. Update the workflow(s) that have only the 'v' flag to also have the 'e' flag
UPDATE vmo_workflow SET allowedoperations = 've' WHERE allowedoperations = 'v';
  1. Exit the Postgres database:
\q
  1.  Restart all the orchestrator pods:
kubectl -n prelude delete pod -l app=vco-app
  1. Monitor the restart progress until you have all the pods running:
kubectl -n prelude get pods -l app=vco-app -w
  1. Press Ctrl + C to cancel the watch command from Step #8. 

Example:image.png

  1. Delete the workflow(s) that are experiencing the problem.