VMware is aware of this issue. See the
Workaround section below for additional information.
Workaround:
Prerequisites
- You have root username and password.
- You have SSH access to the appliances.
- You have backups of the VMware Aria Automation Orchestrator 8.x appliance(s)
- You must back up all VMware Aria Automation Orchestrator appliances, at the same time - simultaneously for all nodes.
- If you are taking the snapshots manually, you must start the snapshots of the second and the third node no more than 40 seconds after you start the snapshots for the first node.
- If VMware Automation Orchestrator is embedded within the VMware Aria Automation appliance, the backup is performed as part of the VMware Aria Automation backup.
Procedure
The database transaction timeout is configurable and may be adjusted using the below steps:
- SSH into the VMware Aria Automation Orchestrator appliance.
- In the Bash terminal, run the following command to change the database transaction timeout value:
vracli vro properties set -k com.vmware.o11n.db.transaction.timeout -v 1200
Note: The above command sets the database transaction timeout to a value of 1200 seconds but it can be any value - set it higher, if needed.
- Wait a few minutes for the Orchestrator pod to start and enter a Running state. You may monitor the services starting using the following command:
kubectl -n prelude get pods -w