Bug ID 501676: Using iControl GlobalLB::WideIP::add_wideip_rule to add iRules to a wide IP may result in error

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Opened: Jan 19, 2015
Severity: 3-Major

Symptoms

Using iControl GlobalLB::WideIP::add_wideip_rule to add iRules to a wide IP which reference objects like pools (typed as of BIG-IPv12.0.0) may result in an error.

Impact

Since a pool of the specified name and of type AAAA does not exist, it fails with an error stating that the iRule validation could not find the specified pool of type AAAA.

Conditions

For example, a rule references a pool name, but specifies no pool type, and this pool only exists in the configuration as a pool of the given name and type A. If the user attempts to add this rule to a given wide IP, and that wide IP exists as both a type A wide IP and a type AAAA wide IP (of the same, specified name), it will result in a failure. This is because the type AAAA wide IP will interpret the rule's pool reference as a reference to a pool with the given name and of type AAAA (the type of the wide IP the rule is on).

Workaround

Use iControl GlobalLB::WideIPV2::add_wide_ip_rule instead, where both the name and the type of wide IP can be specified explicitly.

Fix Information

None

Behavior Change