Migrating from SAAS to on prem Aria Automation the vco-server-app container 3 does gets stuck in CrashLoopBackOff

Products

• VMware Aria Suite

Issue/Introduction

When migrating from SAAS instance to on prem it is possible to migrate data such as endpoints or the VAPI plugin. If there is an issue with the endpoint data it can cause issues starting up the vco-server-app containers leading to the vRO UI not being accessible. 

 

INFO vco [host='vco-app-xxx' thread='localhost-startStop-1' user='' org='' trace=''] {} com.vmware.o11n.plugin.support.model.PluginConfigurationsDumper - Retrieving Plugin[VAPI, xxx] configuration

INFO vco [host='vco-app-xxx' thread='localhost-startStop-1' user='' org='' trace=''] {} com.vmware.o11n.security.SecurityProviderUtils - Using security provider :SUN

 "Retrieving Plugin[VAPI, xxx] configuration"

Environment

Aria Automation Config migration paths from SAAS to on prem offering. 

Cause

The cause is related to migrating information from the SAAS vRO database to the on prem database. 

Resolution

From the Aria Automation server please do the following to resolve this issue: 

Backup Aria Automation

vracli dev psql
\c vco-db

select * from vmo_resourceelement where name like 'ENDPOINT%' and status != 2;
select * from vmo_resourceelement where name like 'METAMODEL%' and status != 2;

delete from vmo_resourceelementcontent where elementid in (select id from vmo_resourceelement where name like 'ENDPOINT%' and status != 2);
delete from vmo_resourceelement where name like 'ENDPOINT%' and status != 2;

delete from vmo_resourceelementcontent where elementid in (select id from vmo_resourceelement where name like 'METAMODEL%' and status != 2);
delete from vmo_resourceelement where name like 'METAMODEL%' and status != 2;

/opt/scripts/deploy.sh

systemctl get pods -n prelude -w   -> monitor that all services come up particularly vco-server-app