Bug ID 1778689: Duplicate OMD alerts during Inaccessible Memory incident

Last Modified: Jun 19, 2025

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

Fixed In:
F5OS-C 1.8.1

Opened: Dec 18, 2024

Severity: 3-Major

Symptoms

During certain conditions where an “Inaccessible Memory” issue occurs, duplicate OMD alerts may accidentally be triggered at the same time due to overlapping OID/alert IDs associated with the same root cause.

Impact

False-positive or duplicate alerts for OMD.

Conditions

This issue arises when an “Inaccessible Memory” incident occurs, resulting in OMD generating redundant alerts “openshiftCertsExpWithinNinetyDays” for the same event, which is causing confusion and unnecessary noise in alert tracking systems.

Workaround

To verify and troubleshoot the issue, you can: 1. Use the confD command 'show cluster cluster-status' to check the cluster's current status. 2. Analyze the openshift.log/velos.log file for any errors or abnormalities related to the incident or cluster health.

Fix Information

The issue has been addressed by implementing enhanced logic in OMD alert generation to eliminate duplicate alerts resulting from overlapping OID/alert IDs. The system now ensures each alert is uniquely identified and mapped to its respective event, preventing redundancy during “Inaccessible Memory” incidents. All configurations have been updated to maintain integrity and consistency.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips