Last Modified: Jan 10, 2023
Affected Product:
See more info
BIG-IP All
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, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
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:/127.0.0.1:42066, method:POST ", "originalRequestBody": "{\"command\":\"save\",\"name\":\"another-test-C2953652-restcurl.ucs\"}", "referer": "/127.0.0.1:42066", "restOperationId": 24434971, "errorStack": [ "java.util.concurrent.TimeoutException: remoteSender:/127.0.0.1:42066, 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.
None.
None
