High volume of "IPVS: rr: TCP - no destination available" console errors after deployment or restart of Aria Automation Orchestrator

Products

• VCF Automation

Issue/Introduction

Following a fresh deployment or restart of the VCF Orchestrator appliance, administrators may observe a continuous, high volume of "IPVS: rr: TCP - no destination available" error messages flooding the appliance console and system logs. This behavior is typically observed during the initial boot sequence, prior to the internal Kubernetes services fully initializing.

Environment

VCF Operations orchestrator 9.x

Cause

The system is functioning as designed during the startup sequence. These errors naturally occur after an appliance restart or initial boot while the underlying Kubernetes IPVS load balancer (kube-proxy) attempts to route internal service traffic. Because the target Kubernetes pods and endpoints have not yet fully initialized and become ready, the routing attempts fail and generate these console messages.

Resolution

The messages are harmless and simply reflect the normal boot sequence of the embedded Kubernetes architecture prior to service availability. As long as the errors do not persist after the appliance is fully operational, the system is perfectly healthy.

VMware Engineering is aware of the cosmetic impact of these messages and plans to suppress them from the console in a future release to prevent unnecessary concern.