Bug ID 652048: TMSH save sys config contains [api-status-warning] that do not correspond to any configuration instances

Last Modified: Apr 28, 2025

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Mar 17, 2017

Severity: 4-Minor

Related Article: K14526459

Symptoms

There are multiple [api-status-warning] logs in /var/log/ltm present. Of these warnings the following do not correspond to existing configuration objects: warning tmsh[1598]: 01420013:4: [api-status-warning] ltm/classification/url-cat-policy is deprecated. warning tmsh[1598]: 01420013:4: [api-status-warning] sys/crypto/ca-bundle-manager is early_access. Logs were generated based off the type, even though there are no instances of that type present. For example: sys/crypto/ca-bundle-manager type is early-access, but there is no instance of this type; still the warning is generated. This is unexpected behavior. Similarly unexpected warning for ltm/classification/url-cat-policy. These [api-status-warning] messages should be created only for types that have been instantiated.

Impact

Excessive [api-status-warning] log message in /var/log/ltm file. The warnings can be ignored.

Conditions

Issue a tmsh save sys config command. Look at the logs in /var/log/ltm corresponding to this operation.

Workaround

None.

Fix Information

Fixed generation of [api-status-warning] messages in /var/log/ltm. These logs were generated for tmsh save sys config operation.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips