Bug ID 502397: Older Epsec system packages are not deleted when new epsec package is installed

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM, Install/Upgrade(all modules)

Known Affected Versions:
11.4.1, 11.5.0, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 12.0.0

Opened: Jan 22, 2015
Severity: 3-Major

Symptoms

Each release of BIG-IP comes with a default epsec system package. If you upgrade and roll-forward the config from previous releases, the older system packages are never deleted. They pile up consuming space on disk.

Impact

Old system packages occupy disk space. And they cannot be deleted via tmsh or UI.

Conditions

Epsec packages must have been installed on the system and the system is upgraded with config roll-forward to newer releases. This can occur on upgrade from any release prior to 12.0.0.

Workaround

None

Fix Information

When new epsec package is installed, the older system packages are automatically deleted.

Behavior Change