Bug ID 1393669: On adding a member to an existing LAG on webUI, the newly added member's speed does not add up to the LAG's "Current Speed" instantly and requires a reload to see the expected response

Last Modified: Oct 21, 2024

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

Known Affected Versions:
F5OS-A 1.7.0

Fixed In:
F5OS-A 1.8.0

Opened: Nov 03, 2023

Severity: 3-Major

Symptoms

The status for the newly added member shows as "down" in the REST response and the newly added member's speed does not add up to the "Current Speed" of the LAG on the webUI/REST response.

Impact

"Current Speed" for the LAG appears stale as it does not reflect the newly added member's speed.

Conditions

Occurs on the webUI when adding a member to an existing LAG.

Workaround

The issue only stays momentarily. If the user refreshes the screen, it shows the LAG's Current Speed appropriately.

Fix Information

N/A

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips