Embedded vRO cluster is out of sync after upgrading the vRA Environment
search cancel

Embedded vRO cluster is out of sync after upgrading the vRA Environment


Article ID: 326159


Updated On:


VMware Aria Suite


You have vRealize Automation high available environment with embedded vRO. When you upgrade it from 7.2.x to 7.3.x, you experience these symptoms:
  • vRO control center cluster configuration settings shows one or more nodes are not synchronized.
  • Restarting the node(s) does not resolve the synchronization issue.


VMware vRealize Automation 7.3.x
VMware vRealize Orchestrator 7.3.x
VMware vRealize Orchestrator 7.2.x
VMware vRealize Automation 7.2.x


This is a known issue where post upgrade is not restarted properly and the new configuration does not get updated in the environment.


To resolve this issue, manually delete the configuration historical data so that it can be repopulated on restart. 
  1. Ensure that you have a valid backup of all vRA environment.
  2. Open an SSH session to all vRA virtual appliances.
  3. Shut down the vRO services on all vRA VA by running this command:
          service vco-server​ stop 
          vco-configurator stop

        4.On the primary vRA VA, log into the postgres database by running these commands:

          su – postgres
          psql vcac

        5.Delete the configuration history table by running this command:

          delete from public.vmo_vroconfigurationhistory;
delete from public.vmo_vroconfiguration;

        6.Logout from the Postgres userby running this command:


  1. Restart the services on all VA nodes by running this command:

           service vco-configurator  start

           vco-server start

        8. Wait for five minutes after restarting services and check the Cluster Configuration setting in the control center again.
        If it is not yet synchronized, restart the vRO configuration services again on all nodes:

           service vco-configurator restart