Bug ID 1572977: Controller pod restart and TMM container restart could result in a condition where restarted TMM pod would not have VLAN and self IP configuration

Last Modified: Oct 19, 2025

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

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: Mar 28, 2024

Severity: 3-Major

Symptoms

If controller pod restarts first and TMM container restarts later or when both restart simultaneously, the restarted TMM would be devoid of VLAN and self IP configuration.

Impact

Restarted TMM pod would not be able to process traffic.

Conditions

A sequential restart of controller pod and TMM container or simultaneous restart of both.

Workaround

Delete the impacted TMM pod so that new pod receives the correct VLAN and self IP configuration.

Fix Information

After restart, controller pushes complete configuration again to all TMMs. Earlier, it was sending only common configuration. It is enhanced to send TMM specific configuration as well.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips