After upgrading to vRealize Orchestrator 7.6 the server service fails to enter a Running state
search cancel

After upgrading to vRealize Orchestrator 7.6 the server service fails to enter a Running state

book

Article ID: 319570

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • After successfully upgrading to vRealize Automation/vRealize Orchestrator 7.6, the environment appears fine within the first 24 hours, then subsequently enters a degraded or stopped state. 
  • The command service vco-server status shows that the Orchestrator server is still running
  • In /var/log/vmware/vco/app-server/server.log the following error is seen:

ERROR {} [BaseController] Error invoking REST [unknown]
com.vmware.o11n.sdk.exception.RestApiException: com.vmware.o11n.service.version.ContentVersionException: org.springframework.dao.IncorrectResultSizeDataAccessException: query did not return a unique result: 2;


Environment

VMware vRealize Automation 7.x

Cause

The table vmo_contentversioncontrol in the embedded PostgreSQL database should only have one row where tenantid is "__SYSTEM".

Resolution

Validate the records within the table with the commands below run from an SSH session to the primary appliance:
  1. su - postgres
  2. psql vcac
  3. select * from vmo_contentversioncontrol;
  4. If there is more than one row for "__SYSTEM" then remove one using the following query as an example:
delete from vmo_contentversioncontrol where id='2';
Note: It should not make a difference which row is removed as long as there is only one row with the following information:
location = /storage/db/vcodata/git/__SYSTEM.git
repositorytype = INTERNAL
systemuser = vco
tenantid = __SYSTEM