Bug ID 1678561: Application health remains stuck in Unknown state.

Last Modified: May 17, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) MA-CM(all modules)

Known Affected Versions:
20.3.0

Opened: Sep 25, 2024

Severity: 1-Blocking

Symptoms

After a successful application deployment the health state does not change to another state in several minutes. The application health remains in "Unknown" state.

Impact

When an application health state remains in "Unknown" it is an indication of a configuration error.

Conditions

A new application deployment will start with a health state of "Unknown" as the data plane is being configured.

Workaround

Find the configuration error: review the f5-fsm-tmm log by way of qkview, debug-sidecar or 3rd party logging tool for configuration errors. Configuration errors can be found by searching for keyword "TMC ERROR" in f5-fsm-tmm log. If an error has been found, delete the application that is in the unknown state. Resolve the configuration error and create new app.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips