Bug ID 556088: In a chassis system with APM provisioned mcpd daemon on secondary blade will restart.

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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.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.1.0, 11.5.4 HF3

Opened: Nov 04, 2015

Severity: 3-Major

Symptoms

Uploading and installing an epsec/Opswat package on a chassis system will result in mcpd restart on the secondary blades.

Impact

All daemons dependent on mcpd will restart

Conditions

Installing a new epsec package in a chassis system is the only condition under which this can happen.

Workaround

None

Fix Information

Prevent validation of epsec package on secondary blades

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips