Bug ID 1592133

Bug ID 1592133: CNF controller logs the error "TMM container is not in Running state" with non-default naming of TMM

Last Modified: Nov 29, 2025

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

Known Affected Versions:
1.3.0

Fixed In:
1.4.0, 1.3.1

Opened: Jun 06, 2024

Severity: 3-Major

Controller logs show multiple entries of the error "TMM container is not in Running state".

TMM is configured incorrectly, traffic disruption can occur.

When CNF is installed with non-default TMM name in the values file. For, example: f5-tmm: tmm: name: <user-defined name>

Configure TMM with the default name. Remove name override from values file.

Added support in the controller to support other TMM names if it is configured in the values file.