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

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 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,,,,

Opened: Aug 03, 2018
Severity: 4-Minor


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


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.


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.



Fix Information


Behavior Change