vRealize Automation 8 Health Check Failing
If your vRA nodes have been marked as unhealthy during a vRLCM pre-upgrade assessment or if your load balancer is marking a node as down when querying its monitoring address then you have come to the right place. The information and steps provided here should in most cases empower you to resolve the issue on your own without the need to engage VMware support. Saving both parties precious time. In this scenario you are likely to see below messages: Ensure vRealize Automation nodes are healthy before upgrade All vRealize Automation nodes should be healthy before upgrade CMDOUT (make: *** [/opt/health/Makefile:67: disk-usage] Error CMDOUT (make: *** [/opt/health/Makefile:60: node-name] Error CMDOUT (make: *** [/opt/health/Makefile:83: podnet-up] Error CMDOUT (make: *** [/opt/health/Makefile:77: k8s-up] Error The Problem A failing vRA health check will typically manifest in one of two ways: It will cause a bad response(500 internal server error) to be returned at t...