Bug ID 796121: Make direct task call to save UCS config results in timeout error

Last Modified: Jan 10, 2023

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Opened: Jun 21, 2019
Severity: 3-Major


For large UCS configurations, making a direct synchronous REST call to create a UCS triggers a REST timeout, for example: restcurl -u user:password -d '{"command":"save","name":"mybackup.ucs"}' /mgmt/tm/sys However, even when you switch to using the asynchronous method you still get a timeout: restcurl -u user:password -d '{"command":"save","name":"mybackup.ucs"}' /mgmt/tm/task/sys/ucs { "code": 400, "message": "remoteSender:/, method:POST ", "originalRequestBody": "{\"command\":\"save\",\"name\":\"another-test-C2953652-restcurl.ucs\"}", "referer": "/", "restOperationId": 24434971, "errorStack": [ "java.util.concurrent.TimeoutException: remoteSender:/, method:POST ", ... ], "kind": ":resterrorresponse" }


REST timeout error occurs. The UCS file may still end up being created, but it is not possible to determine whether the operation was successful using the REST API.


This can be encountered while creating a UCS file via the REST API on a large BIG-IP configuration.



Fix Information


Behavior Change