Bug ID 1169185: TMM may send traffic to unavailable service endpoints when persistence is enabled

Last Modified: Apr 28, 2025

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

Fixed In:
1.7

Opened: Oct 10, 2022

Severity: 3-Major

Symptoms

When TMM processes application traffic using an F5SPKIngressTCP or F5SPKIngressUDP CR and persistence is enabled, TMM may send traffic to unavailable service endpoints after scaling down the application Pods. After the persistence timeout period expires, TMM is able to reselect active pool members.

Impact

Client connections might fail.

Conditions

TMM is procssing application traffic using an F5SPKIngressTCP or F5SPKIngressUDP CR. The spec.persist.mode parameter is set to PERSIST_TYPE_SRCADDR. The serviceDownAction parameter is set to POOLMBR_ACTION_RESELECT. The application Pods experience a scale down event.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips