Bug ID 2265957: GSLB Engine unable to establish TCP connections on OpenShift clusters with OVN-Kubernetes networking

Last Modified: Oct 16, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Known Affected Versions:
2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4

Opened: Apr 14, 2026

Severity: 3-Major

Symptoms

On OpenShift clusters using OVN-Kubernetes networking, GSLB Engine is unable to establish TCP connections for inter-cluster communication. The initial connection handshake begins successfully, but subsequent packets are dropped by the network layer, causing connection failures. GSLB streams between clusters remain in a reconnecting state, and GSLB servers report "No enabled virtual server available" with monitor timeouts.

Impact

GSLB synchronization between clusters fails. Health monitors cannot reach remote virtual servers, causing GSLB to mark all servers as unavailable. DNS load balancing across clusters does not function correctly.

Conditions

OpenShift 4.14 or later cluster using OVN-Kubernetes as the networking plugin. GSLB Sync Group configured with multiple clusters requiring inter-cluster communication.

Workaround

Adjust the network routing rule priority configuration.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips