OpenShift 4: 503 error codes when connecting to routes after migrating to OVNKubernetes
Issue
- After enabling access logs on OpenShift
ingresscontroller
, observing similar error messages for client connections to custom application routes hosted on OpenShift:
2025-07-09T16:12:08.446766+00:00 worker-0-router-zbdfc worker-0-router-zbdfc haproxy[31]: 10.xx.xx.230:53030 [09/Jul/2025:16:12:08.446] fe_sni~ be_edge_http:example-project:target-pod-2/<NOSRV> 0/-1/-1/-1/0 503 2655 - - SCNN 40/20/0/0/0 0/0 "GET / HTTP/1.1"
- Multiple applications/routes unreachable
- Console route is still accessible
- Canary route is still accessible - following steps in this canary-route diagnostics KCS confirms that the canary route is not failing, only custom applications or SOME routes are impacted in the cluster, not ALL.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- OVNKubernetes
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.