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

Products

• VCF Operations/Automation (formerly 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.

 

Environment

VMware vRealize Orchestrator 8.x

Cause

This issue is most commonly caused when a package is created without  'e' 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

3.  Verify the workflow(s) permissions with the below query:
   

   SELECT * from vmo_workflow WHERE name = '<impcted_workflow_name>';

   Note: The allowedoperations can be i.e. "v", "vf" etc.

4. Update the workflow(s) by adding "e" flag to the existing ones in the allowedoperations entry:
   

   UPDATE vmo_workflow SET allowedoperations = 've' WHERE name = '<impcted_workflow_name>';

5. Exit the Postgres database:
   

   \q

6. Restart all the orchestrator pods:
   

   kubectl -n prelude delete pod -l app=vco-app

7. Monitor the restart progress until you have all the pods running:
   

   kubectl -n prelude get pods -l app=vco-app -w

8. Press Ctrl + C to cancel the watch command from Step #7.
9. Delete the workflow(s) that are experiencing the problem.