Bug ID 2288497: CR status falsely reports success when F5-TMM fails to apply configuration

Last Modified: Nov 10, 2026

Affected Product(s):
BIG-IP NEXT CNF None(all modules)

Known Affected Versions:
1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4

Opened: Apr 23, 2026

Severity: 2-Critical

Symptoms

The F5 Ingress Controller marks the CR status READY=true and reports "CR config sent to all grpc endpoints" even when F5-TMM fails to receive or apply the configuration. This behavior creates a false positive because the controller only confirms that it completed the gRPC send without transport-level errors and does not verify that F5-TMM applied the configuration internally.

Impact

Configuration expected to be present on f5-tmm may be missing or partially applied, while the Kubernetes CR status continues to report success. This can result in traffic-affecting misconfiguration (e.g., missing Snatpool, virtual server, or pool objects) with no indication to the customer or operator that remediation is required.

Conditions

This can occur when: - An f5-tmm pod is evicted/rescheduled (during node draining) while configuration is in-flight, causing partial delivery when the connection is re-established. - A transient network interruption occurs while an f5-tmm pod is restarting, resulting in some objects being delivered before the interruption and others after, leaving f5-tmm with a partial configuration set. - f5-tmm receives the gRPC message without a transport error but fails to apply the configuration internally (due to a transient internal error or state inconsistency), most frequently observed in clusters with a large number of f5-tmm replicas.

Workaround

Restart F5ingress. If issues persist after the f5ingress pod restart, the restart removes the missing configuration and forces f5ingress to send a new configuration.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips