vRA 8.6 3-Node Cluster Upgrade - Health checks return 200/OK when backend vRA site is offline.


I am upgrading a test vRA 3-node cluster from 8.6.0 to 8.6.1, using vRSLCM, and I have noticed that the health checks from my load balancer to each individual backend node on http://{node-fqdn}:8008/health still receive 'HTTP/1.1 200 OK' when the underlying vRA site on https://{node-fqdn}/ is actually offline.

Eventually the health checks do fail and the load balancer marks the node as down, but before the upgrade on that node has completed, they start to respond 200/OK again. This happens several times during the upgrade process. 

It doesn't make any sense to me. If the node is down for upgrade I would expect the health check to consistently respond with something other than 200/OK, so the load balancer stops sending traffic to it.

This is my first vRA cluster upgrade experience - is this usual?





0 Kudos
0 Replies