Bug ID 827089: When a SSL Orchestrator app is deployed, tmm errors are logged in /var/log/apm

Last Modified: Dec 13, 2023

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

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3

Fixed In:
16.0.0

Opened: Sep 16, 2019

Severity: 3-Major

Symptoms

If you deploy a layer 3 outbound or inbound app, the deployment will go fine but some errors will be logged in /var/log/apm: err tmm[21184]: 0187005b:3: Access Policy(/Common/ssloP_myTest01.app/ssloP_myTest01_per_req_policy) update: Customization group set can be only assigned to Access policy of type per-request or api-protection notice tmm3[21184]: 01490562:5: /Common/sslo_myTest01.app/sslo_myTest01_end_allow_ag: /Common/sslo_myTest01.app/sslo_myTest01_end_allow agent update can not be resolved.

Impact

The app deploys successfully, but you will see some ambiguous errors in the log. These log messages can be ignored.

Conditions

Provision SSL Orchestrator, deploy l3 outbound or l3 inbound

Workaround

None

Fix Information

Add new condition check, if access policy type is SSL Orchestrator policy, access-per-request cgs wrong assign exception will not be printed in log.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips