This issue is resolved in VMware vRealize Automation 8.2.0, available at
VMware Downloads.
Workaround:
To work around this issue if you do not want to upgrade:
Note: Before proceeding with the steps below, VMware recommends to backup the vRA/vRO system using snapshots without stopping the VMs.
- SSH login to one of the vRA/vRO nodes.
Note: In case of of cluster deployments, complete the steps below:
a. Entify the primary postgres pod, using the "vracli status" command:
For example:
root@vra-appliance [ ~ ]# vracli status | grep primary -B 2
"Total data size": "263 MB",
"Conninfo": "host=postgres-1.postgres.prelude.svc.cluster.local dbname=repmgr-db user=repmgr-db passfile=/scratch/repmgr-db.cred connect_timeout=10",
"Role": "primary",
b. Entify the vRA node running the primary db pod with the "kubectl -n prelude get pods -o wide" command:
For example:
root@vra-appliance [ ~ ]# kubectl -n prelude get pods -o wide| grep postgres-1
postgres-1 1/1 Running 0 15h 10.244.1.156 vra-appliance.domain.com <none> <none>
- SSH login to the vRA/vRO primary DB node.
- Connect to the postgreSQL database and delete the vRO token replay table content:
vracli psql dev
template1=# \c vco-db
You are now connected to database "vco-db" as user "postgres".
vco-db=# TRUNCATE table vmo_tokenreplay;
TRUNCATE TABLE
- On each vRA/vRO appliance node, execute the command below to restore the deleted docker images:
/opt/scripts/restore_docker_images.sh
- Wait until the vRA/vRO cluster is healthy and all pods are in running state.
- On each vRA/vRO appliance node, disable the vRO token replay feature with this command:
rm /data/vco/usr/lib/vco/app-server/extensions/tokenreplay-8.x.0.jar
Note: based on the vRA/vRO product version, the filename is different:
8.1: tokenreplay-8.1.0.jar
8.2: tokenreplay-8.2.0.jar
The file will be created again on each execution of /opt/scripts/deploy.sh. If you need to run the deploy.sh script, delete the tokenreplay jar file again.