Bug ID 1505481: Existing VLAN custom resource is not applied to new TMM pod

Last Modified: Nov 29, 2025

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

Known Affected Versions:
1.2.1

Opened: Feb 08, 2024

Severity: 1-Blocking

Symptoms

Existing VLAN custom resource config is not pushed to a scaled-up TMM pod, specifically to N-1th and/or Nth TMM pods, if there are N pods in the replica set.

Impact

Some of the TMM pods do not receive the VLAN CR config.

Conditions

CNF deployment with VLAN custom resource and TMM replica set scales up from 1 to N.

Workaround

Deploy CNF with TMM replicas N instead of deploying with 1 TMM pod and incrementally scaling up to N pods.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips