Last Modified: Apr 28, 2025
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Fixed In:
1.7
Opened: Jan 10, 2023 Severity: 2-Critical
When TMM pods are Up and in Ready status, f5ingress attempts to send infra CR configs to TMM. Before that transaction ends, the license is made active.
When the license becomes active, f5ingress processes full CR configs and sends it to TMM. It is possible that f5ingress has already opened a connection to the TMM prior to receiving a license update to send infra configs. F5ingress opens more than one connections to TMM at the same time. As a result, "conflict" error is shown in logs.
When TMM pods are Up and in Ready status, f5ingress sends infra CR configs to TMM. In between the start of the transaction and the end of the transaction, the license becomes available and f5ingress tries to send full CR configs to TMM.
TMM pods can be scaled down to zero and scaled back up. Once new pods are Up and Running, f5ingress sends full CR configs and TMM gets configured.
Now, license can be made active at any time and f5ingress handles it even if older transaction is still in process.