Bug ID 1894113: GTM pool with min-members-up-value configured causes synchronisation problems after deleting virtual servers on LTM

Last Modified: Oct 15, 2025

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

Known Affected Versions:
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, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3

Opened: Mar 31, 2025

Severity: 3-Major

Symptoms

GTM pool are not in sync, running list gtm pool does not show the same pool members.

Impact

GTM devices are out of sync.

Conditions

This happens after deleting an ltm virtual that is listed in a gtm server configured with virtual-server-discovery enabled and in which a GTM Pool has min-members-up-value configured. If the deletion of the ltm virtual server (example: tmsh delete ltm virtual vs1) brings the number of virtual server below the configured value with min-members-up-value, then a mismatch occurs with the other GTM on other BIG-IP.

Workaround

Avoid the deletion of ltm virtual if this would bring the number of members below the configured min-members-up-value.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips