Bug ID 708305: Discover task may get stuck in CHECK_IS_ACTIVE step

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.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

Fixed In:
14.0.0, 13.1.0.6

Opened: Feb 28, 2018
Severity: 3-Major

Symptoms

The discover tasks is running periodically after user creates the task. But it may get stuck in the middle steps and fail to run periodically.

Impact

The discover task will periodically pull the OpenID information and update oauth jwt and jwk configurations in MCP. If the task sticks, the jwt and jwk configuration will not sync to the latest version and may cause access policy fail.

Conditions

When HA failover group is set up and a discover task is created on one of the devices.

Workaround

If the task is stuck in any step that is not SLEEP_AND_RUN_AGAIN for more than one minute, manually cancel and delete the task and create the same task again.

Fix Information

Discover task no longer gets stuck in CHECK_IS_ACTIVE step.

Behavior Change