Last Modified: Oct 19, 2025
Affected Product(s):
F5OS F5OS
Fixed In:
F5OS-C 1.8.1
Opened: Dec 23, 2024 Severity: 3-Major
When accessing the confd-cli it may report a different ha-state than that of the bash prompt. For example you may see: syscon-2-standby# [root@controller-2:Active ~]#
Ccsync isn't programmed correctly images and other resources managed by ccsync will not be correctly synced between controllers.
No specific conditions, the issue roots from Vcc-HA using blocking socket I/O that hangs when attempting to program ccsync state. When it hangs, Vcc-HA will hang forever and active/standby state of ccysnc will not be programmed correctly.
Perform docker restart vcc-ha on both controllers.
Updated vcc-ha to use non-blocking socket I/O to insure it cannot get hung when trying to program ccsync. It will instead exit and retry if the timeout is hit.