Bug ID 647091: EPSEC installation failure reason is not logged in certain conditions.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 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, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Feb 23, 2017

Severity: 3-Major

Related Article: K15141540

Symptoms

EPSEC installation fails with no specific reason provided in the error message.

Impact

Difficult to debug actual EPSEC installation failure reason.

Conditions

This happens only when there is a version mismatch between the EPSEC RPM's database and the shared RPM database on the BIG-IP system. Often this happens if a switchboot is issued to activate an earlier version of BIG-IP software from a later version. The RPM database is shared, so on a switchboot, the RPM database version is not downgraded. This causes the subsequent EPSEC installation to fail. Although this is expected behavior, the reason for failure is not logged.

Workaround

None.

Fix Information

The system now logs the EPSEC installation failure reason.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips