Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7
Fixed In:
14.0.0, 13.1.0.8
Opened: Jan 16, 2018 Severity: 3-Major
Finished REST tasks that are not deleted by the client that initiated them are meant to be cleaned periodically. Certain tasks are not included in this cleanup job.
DB space usage grows with each ASM REST task that is not cleaned up.
The following tasks are not reaped automatically if left uncleaned by the REST client that initiated them: From 13.0.x: -- /mgmt/tm/asm/tasks/apply-server-technologies -- /mgmt/tm/asm/tasks/bulk -- /mgmt/tm/asm/tasks/export-policy-template -- /mgmt/tm/asm/tasks/export-requests -- /mgmt/tm/asm/tasks/import-policy-template From 13.1.0: -- /mgmt/tm/asm/tasks/export-data-protection -- /mgmt/tm/asm/tasks/import-data-protection -- /mgmt/tm/asm/tasks/import-certificate -- /mgmt/tm/asm/tasks/policy-diff -- /mgmt/tm/asm/tasks/policy-merge -- /mgmt/tm/asm/tasks/update-enforcer
REST Clients that initiate tasks can delete them after verifying the task has reached a final state.
REST tasks left behind are now be pruned by the DB Cleanup process.