Bug ID 715448: Providing LB::status with a GTM Pool name in a variable caused validation issues

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP DNS, 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, 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, 12.1.3.6, 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

Fixed In:
14.1.0, 14.0.0.3, 13.1.0.8, 12.1.3.7

Opened: Apr 17, 2018
Severity: 3-Major
Related AskF5 Article:
K16055759

Symptoms

When utilizing an LB::status iRule where the GTM Pool name was provided in a variable, instead of directly written into the command, the system posts the following error message: Can't read 'monkey': no such variable.

Impact

Unable to use LB::status iRule.

Conditions

LB::status pool a <Variable containing string>.

Workaround

There is no workaround at this time.

Fix Information

Can now use LB::status iRule command to display the status of a GTM Pool when the name of the pool is provided in a variable.

Behavior Change