Bug ID 1678105: F5OS tenant, TMM crashing after loading a UCS

Last Modified: Mar 12, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Sep 24, 2024

Severity: 2-Critical

Symptoms

If a UCS is loaded on a F5OS tenant and the name of the tenant from where the UCS was saved does not match the tenant name where it is restored.

Impact

The tenant will not become operational because TMM fails to start.

Conditions

- UCS created on a tenant name foo. - UCS restored on tenant named bar.

Workaround

Refer to following steps for workaround: 1. Remove the file "tmm_velocity_init.tcl" in /config/. 2. Perform bigstart restart platform_agent. 3. Ensure a new "tmm_velocity_init.tcl" is created and TMM stops failing.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips