Quantcast
Channel: VMware Communities : Discussion List - vRealize Orchestrator
Viewing all articles
Browse latest Browse all 6251

Migrate vRO 7.6 to vRO 8

$
0
0

Hi,

 

I'm trying to migrate vRO 7.6 to new vRO 8.

I'm following the steps outlined here; Migrating Standalone vRealize Orchestrator 7.x to External vRealize Orchestrator 8.0

I Always get error that SSH Connection is not possible. But when doing "ssh [source appliance]" on new appliance I can connect and Login with provided credentials.

No Firewall between the Systems.

The vro-migrate script is not able to Login to source appliance or check SSH port is open.

vro-migration.log:

++ date

+ echo 'Migration is started at ' Wed Oct 23 10:49:33 UTC 2019

Migration is started at  Wed Oct 23 10:49:33 UTC 2019

+ SRC_VRO_HOST=cis-vro

+ SRC_VRO_ROOTUSER=root

+ set +x

+ TRG_VA_IP=

+ PATH_TO_MIGRATION_JOB_YAML=/tmp/vco-migration-job.yaml

+ touch /tmp/vco-migration-job.yaml

+ cat

+ [[ ! -e /tmp/vco-migration-job.yaml ]]

+ [[ ! -s /tmp/vco-migration-job.yaml ]]

+ kubectl -n prelude scale deployment vco-app --replicas=0

deployment.extensions/vco-app scaled

+ kubectl apply -n prelude -f /tmp/vco-migration-job.yaml

job.batch/vco-migration created

++ kubectl get pods -n prelude -o=name

++ grep vco-migration

++ sed 's/^.\{4\}//'

+ VCO_MIGRATION_POD_NAME=vco-migration-fwcwt

++ kubectl get pods -n prelude vco-migration-fwcwt -o 'jsonpath={.status.conditions[?(@.type=="Ready")].status}'

+ MIGRATION_POD_STATUS_CMD=False

+ [[ False == \T\r\u\e ]]

++ kubectl get po -n prelude vco-migration-fwcwt -o 'jsonpath={.status.conditions[?(@.type=="Ready")].status}'

+ MIGRATION_POD_STATUS_CMD=False

+ echo 'Migration container is not ready.'

Migration container is not ready.

+ sleep 5

+ [[ False == \T\r\u\e ]]

++ kubectl get po -n prelude vco-migration-fwcwt -o 'jsonpath={.status.conditions[?(@.type=="Ready")].status}'

+ MIGRATION_POD_STATUS_CMD=True

+ echo 'Migration container is not ready.'

Migration container is not ready.

+ sleep 5

+ [[ True == \T\r\u\e ]]

+ set +x

Wed Oct 23 10:49:45 UTC 2019 : Start installation of vco configuration cli.

Preparing...                          ################################# [100%]

Updating / installing...

   1:vco-cfg-cli-8.0.0.1570646260-1483################################# [100%]

Wed Oct 23 10:49:46 UTC 2019 : Installation of vco configuration cli is completed

Wed Oct 23 10:49:46 UTC 2019 : Verify ssh connection to source host is possible

Wed Oct 23 10:49:46 UTC 2019 : IS_SSH_CONNECTION=

Wed Oct 23 10:49:46 UTC 2019 : Verify connection on port 22 to the source host machine is possible.

Wed Oct 23 10:49:46 UTC 2019 : Connection to cis-vro on port 22 is not possible.

Wed Oct 23 10:49:46 UTC 2019 : Please verify that the correct hostname is provided: cis-vro.

Wed Oct 23 10:49:46 UTC 2019 : Please make sure that port 22 on the source host machine is opened while making the migration.

Wed Oct 23 10:49:46 UTC 2019 : If the port is opened then verify that the correct username and password are entered.

command terminated with exit code 1

+ startVcoDeploy

+ echo 'Start vco-app containers again.'

Start vco-app containers again.

+ kubectl -n prelude scale deployment vco-app --replicas=1

deployment.extensions/vco-app scaled

+ echo 'Delete migration job artifacts.'

Delete migration job artifacts.

+ kubectl delete job -n prelude vco-migration

job.batch "vco-migration" deleted

+ rm /tmp/vco-migration-job.yaml

+ rm /tmp/vco_migration_on

++ date

+ echo 'Migration finished at' Wed Oct 23 10:49:47 UTC 2019

Migration finished at Wed Oct 23 10:49:47 UTC 2019

+ set +x

Container migration script failed.

 

 

Any ideas what would be causing this?


Viewing all articles
Browse latest Browse all 6251

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>