Bug ID 1858617: Users unable to login after reboot with LDAP group configured

Last Modified: Feb 05, 2026

Affected Product(s):
F5OS Install/Upgrade, Velos(all modules)

Known Affected Versions:
F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2

Opened: Mar 20, 2025

Severity: 2-Critical

Symptoms

- CLI/GUI access for all roles other than admin and root is denied - The GUI permit user authentication and then immediately terminate the session; for more information, refer to https://cdn.f5.com/product/bugtracker/ID1933645.html. - Repeated log messages from user-manager in platform.log / velos.log with an error of "Lost connection to ConfD" / "Socket to ConfD is closed": user-manager[17]: priority="Err" version=1.0 msgid=0x6802000000000001 msg="cdb_get failed for" ATTRIBUTE="rolename" ERRNOSTR="Lost connection to ConfD" LASTERR="Socket to ConfD is closed" ERRNO=45.

Impact

Users with roles other than admin and root cannot login using CLI or GUI

Conditions

- LDAP system authentication is enabled - A LDAP group is defined for a role in the system - Queries to the LDAP server take a long time, for example due to connection timeouts or LDAP referral chasing. This issue can also occur when the system is rebooted if user-manager tries to perform LDAP queries before the management network is accessible.

Workaround

1. Restart the appropriate user-manager container (system_user_manager on rSeries appliances, controller-userman for VELOS system controllers, and partition<ID>_user_manager for VELOS partitions) 2. Disable LDAP system authentication or remove the LDAP group definitions, and then restart the user-manager container. This will restore connectivity for locally-defined users.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips