Bug ID 430012: iRule validation checks accessing object in different partition

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.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.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Opened: Sep 06, 2013
Severity: 2-Critical
Related AskF5 Article:
K15339

Symptoms

In version 10.x, you can configure an iRule to load balance to a pool on a different administrative partition than the virtual server, and the virtual server showed up as available/green status. After upgrading to version 11.x, the virtual server stays in an unknown state, even though the pool monitor is successful and the pool is up and passing traffic.

Impact

The virtual server might get into an unknown state when a pool in different partition is selected by an iRule. If an iRule accesses object that is in a different partition other than /Common, validation can fail.

Conditions

This occurs when iRules from previous versions of the software reference objects in a different partition that is not the /Common partition.

Workaround

Do not use iRules to access objects in different partitions other than /Common.

Fix Information

None

Behavior Change