Bug ID 2218565: Controller boot up in rare conditions can impact blade management network after failover

Last Modified: Jun 25, 2026

Affected Product(s):
F5OS F5OS-C(all modules)

Known Affected Versions:
F5OS-C 1.8.2

Opened: Jan 30, 2026

Severity: 3-Major

Symptoms

A rare race condition in the vcc-lacpd process can prevent a system controller failover correctly setting the LACP status for LACP based link aggregations. This condition is easily identifiable if the log msgid=0x6602000000000003 originating from vcc-lacpd process is seen since the last controller reboot.

Impact

Blade management network can be impacted which can cause a variety of issues, including blade reboot loops on partition upgrade. If a management aggregation on the controller front panel management ports is configured for LACP, this aggregation may also be impacted.

Conditions

Controller reboot. It is more likely though still extremely rare to occur if vcc-lacpd process restarts independently of a controller reboot.

Workaround

Restart the affected vcc-lacpd process via docker restart cc-lacpd.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips