Bug ID 1595053: Unable to delete f5-big-dns-apps CR from TMM container

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 12, 2024

Severity: 3-Major

Symptoms

On DNSApp CR deletion, the configuration is not removed from TMM if ICMP or TCP monitor is enabled in the CR. The corresponding virtual server should be deleted from the TMM, but virtual server is available. Use the following steps to check the virtual server: 1. Create a DNSApp CR with ICMP or TCP monitor enabled. 2. Confirm the corresponding virtual server is created on TMM by using tmctl. 3. Delete the CR. 4. Confirm the corresponding virtual server is not present on TMM by using tmctl.

Impact

Configuration does not work for API objects that do not exist. Traffic will not work when sent to a virtual server that does not exist.

Conditions

- DNSApp CR deletion

Workaround

None

Fix Information

Objects with type ltm_icmp_monitor and ltm_tcp_monitor have been replaced with the correct object type ltm_monitor.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips