Bug ID 687172: Pools do not appear as expected after deploying iApp via iWorkflow

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
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, 12.1.3.7, 12.1.4, 12.1.4.1, 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, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6

Opened: Oct 04, 2017
Severity: 3-Major

Symptoms

Only two of three pools are visible in the iApp view on the BIG-IP system after deploying via iWorflow 2.2, though the pool can be found as expected in the Pools view.

Impact

Unreliable query response can result in unexpected behavior.

Conditions

-- After deploying via iWorflow 2.2. -- Using iApp to view configured pools.

Workaround

Do not rely on the iApps Component View, but inspect BIG-IP (management GUI) Local Traffic pages such as Local Traffic :: Pools : Pool List or examine the /config/bigip.conf file to ascertain whether a desired BIG-IP configuration has been created.

Fix Information

None

Behavior Change