Bug ID 428072: iRules referring to pool by full path/folder name

Last Modified: Sep 13, 2023

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

Known Affected Versions:
10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1

Fixed In:
11.6.0, 11.5.2, 11.4.1 HF9, 10.2.4 HF12

Opened: Aug 15, 2013

Severity: 3-Major

Related Article: K15940

Symptoms

If an iRule refers to a pool by the full path, /folder/pool name, the virtual server status does not reflect the pool's status.

Impact

While traffic can still be served to the pool_member despite the virtual server status, for changes at the virtual server level (for example, route health injection), the system needs a reliable virtual server health status.

Conditions

This occurs when the iRule uses the full path name for the pool.

Workaround

Remove the folder path and reference the pool by name only within the iRule.

Fix Information

If an iRule refers to a pool by leaf name (without the full path), the virtual server status now reflects the pool's status.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips