vRA 8.12.2

[38aytac38]

Hi,

We upgraded from 8.9 to 8.12.2 but now there seems to be a problem.

There are pods restarting almost every 10 minutes I already tried to reconfigure the internal ip's and also did redeploy but the problem still exists.

These are the pods and the errors

catalog-service-app
cgs-service-app
tango-blueprint-service-app

catalog-service-app

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 62m (x3 over 119m) kubelet Readiness probe failed: Get "http://10.245.0.29:8000/actuator/health/readiness": dial tcp 10.245.0.29:8000: connect: connection refused
Warning BackOff 44m (x7 over 109m) kubelet Back-off restarting failed container
Normal Pulled 22m (x12 over 130m) kubelet Container image "catalog-service_private:8.12.2.31329" already present on machine
Warning Unhealthy 12m (x13 over 119m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Normal Created 11m (x14 over 130m) kubelet Created container catalog-service-app


tango-blueprint-service-app

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 16m (x270 over 116m) kubelet Readiness probe failed: Get "http://10.245.0.31:8080/actuator/health/readiness": dial tcp 10.245.0.31:8080: connect: connection refused

cgs-service-app

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 37m (x5 over 105m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Warning Unhealthy 5m11s (x10 over 47m) kubelet (combined from similar events): Readiness probe failed: HTTP probe failed with statuscode: 503
Warning Unhealthy 2m21s (x815 over 120m) kubelet Readiness probe failed: Get "http://10.245.0.25:8090/content/api/health": dial tcp 10.245.0.25:8090: connect: connection refused

[Eduardo Suarez]

Hello,

How are you trying to redeploying the internal IPs? via VMware Aria Suite Lifecycle?

Can you please run the commands of this kb https://kb.vmware.com/s/article/94871? And share the output they may be helpful 

[38aytac38]

Hi,

Yes I did redploy them through VMware Aria Suite Lifecycle.

Redploying the internal IP's didn't give me an error but there are some pods that are restarting almost every 10/15 minutes.

 

 

[Eduardo Suarez]

Is it possible to revert to snapshot before the internal IP change?

Then try that from Vmware Aria Suite Lifecycle?

 

[Eduardo Suarez]

or following this doc should work.

https://docs.vmware.com/en/VMware-Aria-Automation/8.12/Installing-Configuring-Automation-Orchestrator/GUID-7690AF2E-AA1C-40F9-A224-CEA7F2D1F7A7.html

[38aytac38]

I already did revert to snapshot before the internal IP change.
But I think the error problem occurred after the upgrade to 8.12.2 and unfortunately it deleted that snapshot because it was upgraded successfully.

I also tried to manuelly upgrade to 8.13.1 but that also won't work because not all pods are healthy