Bug ID 1566757: Standalone SSL Orchestrator thinks it has a peer device

Last Modified: Apr 28, 2025

Affected Product(s):
iApps SSLO(all modules)

Opened: Mar 18, 2024

Severity: 2-Critical

Symptoms

On the SSL Orchestrator GUI, there is a warning banner saying "One or more SSL Orchestrator configurations are in an incorrect state. Look for errors in /var/log/restnoded/restnoded.log for corrective action to those configurations before making additional changes to avoid further errors..." In /var/log/restnoded/restnoded.log the following logs appear "Mon, 18 Mar 2024 21:37:56 GMT - severe: [SSL Orchestrator] App Name: <name> App Type: Policy Mon, 18 Mar 2024 21:37:56 GMT - severe: [SSL Orchestrator] Device <Management IP> is having hanging MCP objects and need cleanup Mon, 18 Mar 2024 21:37:56 GMT - severe: [SSL Orchestrator] Device <Cluster IP> is in good state Mon, 18 Mar 2024 21:37:56 GMT - severe: [SSL Orchestrator] App config corrupted, please resolve before proceed" and "Mon, 18 Mar 2024 21:37:57 GMT - severe: [DeviceAuthTokenManager.retrieveSecurityToken] Failed to authenticate request to none. Remote device has not been discovered. Mon, 18 Mar 2024 21:37:57 GMT - severe: Failed to send identifiedDeviceRequest: Error: Failed to authenticate request to none. Remote device has not been discovered."

Impact

SSL Orchestrator GUI shows a warning message to not make any additional changes to avoid further errors. Deployments also fail due to SSL Orchestrator trying to negotiate with a non-existent peer.

Conditions

BIG-IP is a VCMP guest with at least 1 cluster. The 1 cluster has a specific IP address that differs for the default cluster IP address.

Workaround

There is no workaround.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips