Bug ID 1316097: LAGs not programmed when adding VLAN to LAG

Last Modified: May 29, 2024

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.6.0, F5OS-A 1.5.2

Opened: Jul 03, 2023

Severity: 3-Major


Traffic from a LAG is not reaching the tenant.


LAGs are not programmed; traffic doesn't reach tenant.


1) Add a VLAN to a LAG and add that VLAN to a tenant in the same commit. 2) Configuration read following blade reboot.


Workaround for condition (1): Add the VLAN to the LAG, commit; then add the VLAN to the tenant.

Fix Information

Fix usage of mutexes to prevent deadlock with LAG programming is happening in parallel with VLAN programming.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips