Pushing changes to some remote git repos in Aria Orchestrator 8.x take a long time and sometimes do not successfully save at all

search cancel

book

calendar_today

VMware Aria Suite

Changes on Aria Orchestrator git integration are sporadically lost.
Audit Logs show evidence the workflow or action was saved, but after few hours the changes are no longer showing visually in schema or in Version History.
Code modifications are preserved when the resource (e.g. workflow) is saved (SAVE button).
However when pushed to the remote GitHub repo by clicking the VERSION button, the code modifications are lost.
The git push itself takes a long time. Checking the vco logs in this time shows there are very many add/delete operations which seem unnecessary.
This issue is specific to a given git repository: creating a new one and pushing/pulling changes should see any edits merge within minutes and persist on remote branch.
There may be a large time gap between subsequent com.vmware.o11n.git.remote.RemoteCommandBuilder messages in the Orchestrator log file /services-logs/prelude/vco-app/file-logs/vco-server-app.log

In some scenarios, unnecessary add/delete operations can take a long time to process and cause loss of data in the git repo.

An optimization of the git code is found in Patch 1 for Aria Orchestrator 8.18.1:
- VMware Aria Automation 8.18.1 Cumulative Update - Patch 1
If this does not solve the slow push/pull, there may be an issue in the local git history on Orchestrator.
- To clear the local git history what we can do is move/remove the __SYSTEM.git directory:
  - mv /data/vco/usr/lib/vco/app-server/data/git/__SYSTEM.git /home/root/BACKUP__SYSTEM.git
- When a user then navigates to the Git History page in Orchestrator, the local repository will be recreated
- The remote repo can now be pulled to get the latest changes locally
If the issue is still not resolved, please copy the remote repository to a fresh directory and re-initialize this with git (create new repository)

thumb_up Yes

thumb_down No