Last Modified: Apr 28, 2025
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Known Affected Versions:
1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7
Fixed In:
1.9.2, 1.7.8
Opened: Apr 04, 2024 Severity: 3-Major
Multiple TMMs are configured with same self IP address. TMM only picks up the self IP which was sent first and ignores the subsequent updates received from F5Ingress controller.
F5Ingress fails to persist information (TMM-selfIP assignment) in its persistent configmap. Due to which it keeps attempting to re-configure the TMM with new self IP assuming the TMM was not previously configured. Eventually, it assigns distinct self IPs to all TMM pods and also persists the accurate information in configmap. But TMM only picks up the self IP which was sent first and ignores the subsequent updates. TMMs with duplicate self IPs will not process the traffic.
When TMM pod takes too long to be ready and the condition could be hit when there are more number of TMM pods in a rolling upgrade scenario.
Scale down the TMM pods to 0 and bring them back up, all TMMs will have unique self IP addresses assigned to them.
F5Ingress controller is hardened with consistent way of identifying the ready TMMs. Based on that, managing self IPs across ready TMMs is refactored and fixed.