Bug ID 707207: iRuleLx returning undefined value may cause TMM restart

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
14.1.0, 14.0.0.5, 13.1.0.8, 12.1.3.6

Opened: Feb 20, 2018
Severity: 2-Critical

Symptoms

When an iRulesLX rule returns an undefined value, TMM may restart. An example of an undefined value is one where its jsonrpc v2.0 representation is missing required fields, such as "result".

Impact

Traffic is interrupted.

Conditions

iRulesLX is licensed, and a rule is run that returns an undefined value.

Workaround

There is no workaround at this time.

Fix Information

A TMM restart resulting from an iRulesLX rule returning an undefined value was fixed.

Behavior Change