Last Modified: Apr 28, 2023
Affected Product(s):
BIG-IP SSLO, TMOS
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2
Opened: Jun 30, 2020 Severity: 3-Major
Attempting to configure and deploy an SSL Orchestrator configuration may result in a configuration processor timeout error.
The operation fails, resulting in a configuration processor timeout error. The BIG-IP administrator cannot configure and deploy an SSL Orchestrator configuration.
When the TMOS control plane is taking a relatively high amount of CPU processing due to intense REST framework management workflows, any attempt to configure and deploy an SSL Orchestrator configuration using the guided configuration user interface, might take longer than the default 30 seconds timeout.
1. Edit the /var/config/rest/iapps/f5-iappslx-ssl-orchestrator/nodejs/gc/orchestratorConfigProcessor.js file: vi /var/config/rest/iapps/f5-iappslx-ssl-orchestrator/nodejs/gc/orchestratorConfigProcessor.js 2. Locate the var _createComponentBlock = function(...) and locate the following line inside the function body (line ~1290): requestBody.state = "BINDING"; 3. Add the following after the 'requestBody.state' line: requestBody.configProcessorTimeoutSeconds = 120; 4. Save the edited file. 5. Restart the restnoded daemon: bigstart restart restnoded
None
