Bug ID 506101: Asynchronous Tasks for Long-Running command control

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
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

Fixed In:
12.0.0

Opened: Feb 11, 2015
Severity: 2-Critical
Related AskF5 Article:
K16758

Symptoms

Long-running operations via the iControl/REST interface might lead to timeouts and non-responsiveness to new requests while the operation completes, with no way to return the result. While transactions can mitigate this by permitting polling on the status of the transaction, not all operations are permitted in transactions.

Impact

This makes automated control problematic, as it removes control over long-running operations.

Conditions

Heavily loaded systems might result in some commands, particularly save sys config, or save sys ucs, taking so long to complete that they time out. Until the operation completes, further operations can not be started by the same user.

Workaround

Where possible, run long-running iControl/REST commands in transactions.

Fix Information

Long-running operations via the iControl/REST interface no longer lead to timeouts and non-responsiveness to new requests while the operation completes.

Behavior Change