Bug ID 1123205: [APM][EPSEC]OPSWAT / EPSEC - Multiple epsec packages are marked as 'System Package' after upgrade

Last Modified: Dec 20, 2023

Affected Product(s):
BIG-IP APM, Install/Upgrade(all modules)

Known Affected Versions:
14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,, 17.0.0,,

Opened: Jun 30, 2022

Severity: 4-Minor


Multiple epsec packages are marked as system packages.


By design, epsec packages marked as 'System Package' and cannot be deleted. Consequently, old epsec package marked as 'System Package' cannot be deleted. The Delete button is greyed out.


-- A BIG-IP upgrade is performed. -- The system epsec package included in the upgraded BIG-IP version is different than the one currently used.


While packages are getting updated, mcpd may fail to fetch the date correctly, ending with both the old and the new epsec versions to show 'system-package' as 'true'. In order to correct the status, force a mcpd reload. K13030: Forcing the mcpd process to reload the BIG-IP configuration https://support.f5.com/csp/article/K13030 K21175584: Removing unnecessary OPSWAT EPSEC packages from the BIG-IP APM system https://support.f5.com/csp/article/K21175584

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips