mammadshah
Contributor
Contributor

vRealize Automation upgrade to 8.2 inventory sync issue

HI,

After successful upgrade of Lifecycle Manager from 8.1 to Version : 8.2.0.23 Build : 16982087 and Identity manager to 3.3.2. 

I have started to upgrade vRealilze Automation, during the upgrade I have faced disk space issue and I shutdown the Automation appliance. 

After that I increased the disk space on vCenter server and executed commands to increase the lvm inside the appliance of vRA,

vracli disk-mgr resize
/usr/sbin/resize2fs .....

vRA disk volumes were successfully resized and I have started to perform "Inventory Sync" but the request failed immediately.

I have restarted all appliances but this didn't help.

0 Kudos
4 Replies
lnairn
VMware Employee
VMware Employee

Hi @mammadshah ,

Can you verify what is the vRA status with vracli service status ? Is there anything failing?

Regards,

Leandro.

0 Kudos
ppachniak
Contributor
Contributor

I'm actually experiencing the exact same issue after rebooting the vRA appliance prior to an upgrade attempt to 8.2.  Everything is healthy and running (see command results below).  When I go to the Environment page for the vRA environment, the Product details are empty.  The results of the results for the inventory sync are also empty (we have to click the exclamation point to find the error).

ppachniak_0-1605655995929.png

ppachniak_1-1605656039665.png

 

ppachniak_2-1605656081538.pngppachniak_3-1605656081590.png

 

root@servername [ ~ ]# kubectl -n prelude get pods
NAME READY STATUS RESTARTS AGE
abx-service-app-74478bc89c-fkfcv 1/1 Running 1 68d
approval-service-57dd4c8dc9-ccwdc 1/1 Running 1 68d
assessment-service-app-77c9944456-zhm7f 1/1 Running 1 68d
automation-ui-app-58bbdcd5f-9nrqv 1/1 Running 1 68d
blueprints-ui-app-849c88547f-fnwkk 1/1 Running 1 68d
catalog-service-app-69d594ffb7-k9tz2 1/1 Running 1 68d
catalog-ui-app-dbb8d6d98-mgmlz 1/1 Running 1 68d
cgs-service-55d76f8984-8rxv6 1/1 Running 1 68d
cgs-ui-app-6cdcc65db7-vwmgr 1/1 Running 1 68d
cmx-service-app-856fbbd487-n8fv5 1/1 Running 1 68d
codestream-app-c7995bffb-qvg4x 1/1 Running 1 68d
deployment-ui-app-6b6d8d55c8-hq6vt 1/1 Running 1 68d
docker-registry-5bf9b47b68-5xxrz 1/1 Running 2 68d
docker-registry-proxy-57bb4b45bf-6ngpd 1/1 Running 5 68d
ebs-app-7577dd5c5b-zr6pk 1/1 Running 1 68d
extensibility-ui-app-b9d69cbd9-m425t 1/1 Running 1 68d
form-service-app-fb578b66f-86gwb 1/1 Running 1 68d
identity-service-app-fc9cdb7cc-vcgcv 1/1 Running 1 68d
identity-ui-app-6fccc5f87c-dqbzv 1/1 Running 1 68d
landing-ui-app-6f7d59d84d-l9jz8 1/1 Running 1 68d
migration-service-app-767f977f6b-fxqnr 1/1 Running 1 68d
migration-ui-app-674668fd45-56g4g 1/1 Running 1 68d
nginx-httpd-app-c59965577-6jjsg 1/1 Running 1 68d
no-license-app-85bc44cc-f668j 1/1 Running 1 68d
orchestration-ui-app-6744d98cd5-zspnq 1/1 Running 1 68d
pgpool-b6f4fd9cd-wrntp 1/1 Running 1663 68d
pipeline-ui-app-544649545f-4rvtd 1/1 Running 1 68d
postgres-0 1/1 Running 1 68d
project-service-app-5f4564ccbc-p7lcj 1/1 Running 1 68d
provisioning-service-app-69bcd9fbd6-hhkf5 1/1 Running 1 68d
provisioning-ui-app-7555fb8f6c-v8h9g 1/1 Running 1 68d
proxy-service-5c78496786-r8b2l 1/1 Running 1 68d
quickstart-ui-app-7b5b6d654d-fsmh7 1/1 Running 1 68d
rabbitmq-ha-0 1/1 Running 1 68d
relocation-service-app-6dfd9977d-8bhhh 1/1 Running 1 68d
relocation-ui-app-59bb67d8b5-tkfr4 1/1 Running 1 68d
symphony-logging-7fc8cdbd95-8ghwz 1/1 Running 1 68d
tango-blueprint-service-app-7464895c78-xlbm7 1/1 Running 1 68d
tango-vro-gateway-app-696fb9d6f8-7rllk 1/1 Running 1 68d
terraform-service-app-868fcdf97b-kqbtg 2/2 Running 2 68d
user-profile-service-app-75c7b486db-4mjgn 1/1 Running 1 68d
vco-app-6d54c7c78b-45nw8 3/3 Running 3 68d


root@servername [ ~ ]# vracli service status
Service State Health Nodes CPU Memory Persistent Disk
------------------------- ------- -------- ------- ------ -------- -----------------
Infrastructure

docker-registry Started Healthy 1/1 0.01 % 12 MB
docker-registry-proxy Started Healthy 1/1 0.01 % 2 MB
endpoints Started Healthy 1/1 0.01 % 18 MB
etcd-service Started Healthy 1/1 0.1 % 93 MB
health-reporting-service Started Healthy 1/1 0.01 % 4 MB
ingress-ctl Started Healthy 1/1 0.1 % 41 MB
kube-apiserver Started Healthy 1/1 0.21 % 323 MB
kube-controller-manager Started Healthy 1/1 0.15 % 65 MB
kube-dns Started Healthy 1/1 0.02 % 15 MB
kube-flannel-ds Started Healthy 1/1 0.03 % 27 MB
kube-proxy Started Healthy 1/1 0.01 % 25 MB
kube-scheduler Started Healthy 1/1 0.02 % 19 MB
kubelet-rubber-stamp Started Healthy 1/1 0.01 % 17 MB
openfaas Started Healthy 1/1 0.03 % 29 MB
postgres Started Healthy 1/1 0.41 % 1702 MB 4 GB
predictable-pod-scheduler Started Healthy 1/1 0.15 % 4 MB
proxy-service Started Healthy 1/1 0.01 % 143 MB
rabbitmq-ha Started Healthy 1/1 4.16 % 151 MB 0 GB
symphony-logging Started Healthy 1/1 0.16 % 217 MB 3 GB
tiller-deploy Started Healthy 1/1 0.01 % 20 MB

Applications

abx-service Started Healthy 1/1 0.1 % 815 MB
approval-service Started Healthy 1/1 0.09 % 877 MB
catalog-service Started Healthy 1/1 0.12 % 1413 MB
cgs-service Started Healthy 1/1 0.05 % 998 MB
cmx-service Started Healthy 1/1 0.05 % 689 MB
codestream Started Healthy 1/1 0.05 % 887 MB
ebs Started Healthy 1/1 0.3 % 865 MB
form-service Started Healthy 1/1 0.02 % 592 MB
identity-service Started Healthy 1/1 0.03 % 736 MB
migration-service Started Healthy 1/1 0.03 % 604 MB
no-license Started Healthy 1/1 0.01 % 6 MB
project-service Started Healthy 1/1 0.02 % 735 MB
provisioning-service Started Healthy 1/1 0.1 % 1428 MB
relocation-service Started Healthy 1/1 0.05 % 502 MB
tango-blueprint-service Started Healthy 1/1 0.1 % 846 MB
tango-vro Started Healthy 1/1 0.05 % 1016 MB
terraform-service Started Healthy 1/1 0.04 % 436 MB
ui Started Healthy 1/1 0.13 % 34 MB
user-profile-service Started Healthy 1/1 0.03 % 427 MB
vco Started Healthy 1/1 0.08 % 1910 MB 0 GB

0 Kudos
mammadshah
Contributor
Contributor

I have restored the whole environment and extend the drive of vRA 8.1 applied the changed a patch on vRLCM prior to upgrade to 8.2.

After that the upgrade was successful.

 

0 Kudos
ppachniak
Contributor
Contributor

@mammadshah When you say you restored the whole environment, did you have snapshots of the appliance(s) that you reverted to?  Or are you saying you decommissioned and reinstalled the environment 8.1 environment (and if so, did you reinstall vRLCM, vIDM, and vRA, or only vRA)?  You also mentioned that you applied a patch to vRLCM prior to the 8.2 upgrade.  What patch was applied?

0 Kudos