When attempting a pull from master repository I get the error "Error: The workflow name contains invalid characters (\, /).Name: null. ID: null"

Products

• VMware Aria Suite

Issue/Introduction

 

After upgrading to vRA 8.18.x, the action for Extensibility  in vRO  that is used to push it to GIT functionality  is giving error after upgrading vRA       “Error: The workflow name contains invalid characters (\, /).Name: null. ID: null”.      

Symptoms:

       1. Workflow Subscriptions is missing (Extensibility > Subscription ComputePostProvisioning is missing)         

           Extensibility> Action/Workflow >  (In the above screen, Click ADD for /Action/Workflow, and the next screen does not even show up that action/workflow in the list)

       2.Embedded-vRO Git History shows “Error: The workflow name contains invalid characters (\, /).Name: null. ID: null”.  as shown in the screen below;

   3.  Missing Workflow.xml 

 

Environment

Customer has a Dev and a Production Environment.

Customer created  an Extensibility action in vRO that using to push the Dev environment objects to GIT.

After upgrading to vRA 8.18.x,  gets an  while trying the git actions: "Error: Rebase on top of remote failed! Status is: STOPPED".

Cause

The new version for the GIt push/pull from external repository functionality is broken.

Resolution

Workaround:

    Export the local vRO base repository from one of the virtual appliances in the cluster setup to  local machine where they had Git installed.

    Create a staging area for the local vRO base repository on the local machine by performing:
         > git clone <relative_path>/__SYSTEM.git
    

    In the staging area push a revert of the commit, introducing the “stub” workflow.xml file by performing:
        1. > git revert <commit_SHA_hash>
        2. > git push
    

   Make the production Aria Orchestrator to pull from new branch by Executing a pull. If Rebase errors occurs resolve them on an individual basis. If needed:

     Replace the local vRO base repository in all of the nodes in the cluster with the updated one which now contains the reverting commit in its history that was generated in step 3. 
     Correct any variables which lost connection with orchestrator configurations or needed to be set to production values