Bug ID 522871: [TMSH] nested wildcard deletion will delete all the objects (matched or not matched)

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4

Opened: May 12, 2015
Severity: 3-Major
Related AskF5 Article:
K13764703

Symptoms

Nested wildcard deletion deletes all of the objects (matched or not matched).

Impact

All objects are deleted, instead of those targeted for delete.

Conditions

Use deletion in a nested TMSH command. For example: tmsh modify gtm server GTM1 virtual-servers delete {f*} This deletes all virtual servers even if none of the servers match. The same issue applies to pool members.

Workaround

None.

Fix Information

Nested wildcard deletion now deletes matched objects only.

Behavior Change