Bug ID 739157: Failure to create ASM policy from non-existent template must be syslog-reported

Last Modified: Sep 14, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Opened: Aug 03, 2018

Severity: 4-Minor

Symptoms

An expected failure to create ASM policy from a non-existent template is not reported as an error to syslog.

Impact

Failure to create the ASM policy is not reported as an error to syslog, although you might have seen errors similar to the following INFO-level messages in /var/log/ts/asm_config_server.log: ---------------------------------------------------------------------- asm_config_server.pl|INFO|Jul 31 18:34:17.724|18140|F5::ASMConfig::Handler::handle_error,,Failed add policy using on nonexistent record for PolicyTemplate asm_config_server.pl|INFO|Jul 31 18:34:17.725|18140|F5::ASMConfig::Handler::log_error_and_rollback,,Could not add policy using the Policy Template 'Nonexistent_template', No matching record was found.

Conditions

An ASM policy was created in MCP using a non-existent template, such as when device group sync is enabled, but ASM sync is not configured.

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips