Bug ID 1145961: DB entries may be deleted after the timeout interval even though the session is active

Last Modified: Oct 19, 2025

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

Fixed In:
1.7

Opened: Sep 05, 2022

Severity: 3-Major

Symptoms

When the F5SPKIngressTCP or F5SPKIngressUDP CR spec.persist.mode parameter is set to PERSIST_TYPE_SRCADDR, persistence records may be deleted from the dSSM database after the configured timeout period, even though the session is active. The database entry should reset to the timeout value when connection responses are received.

Impact

Clients may load balance through TMM to unexpected service endpoints (pool members).

Conditions

Install an F5SPKIngressTCP or F5SPKIngressUDP CR. Set the spec.persist.mode parameter to PERSIST_TYPE_SRCADDR. Notice connections may load balance to different service endpoints after the configured timeout period, even while the session is active.

Workaround

no workaround.

Fix Information

.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips