Bug ID 2285041: The module-communication-error not clearing post-recovery

Last Modified: Jun 25, 2026

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

Known Affected Versions:
F5OS-C 1.8.2

Opened: Apr 20, 2026

Severity: 3-Major

Symptoms

A shared commError flag in the VPC and VFC health monitoring tasks caused a race condition when tracking communication errors across controllers.

Impact

This led to scenarios where a module communication error status was not cleared even after recovery.

Conditions

A shared commError flag caused a race condition where a communication error in one PSU controller could be incorrectly cleared by another PSU controller, leaving the original controller's error uncleared even after recovery.

Workaround

Restart diag-agent using the below command docker restart diag-agent

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips