-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.16, 4.17
-
Important
-
No
-
3
-
OTA 252, OTA 253, OTA 254
-
3
-
Proposed
-
False
-
-
Release Note Not Required
-
In Progress
Using the alerts-in-CLI PoC OTA-1080 show relevant firing alerts in the OTA-1087 section. Probably do not show all firing alerts.
I propose showing
- Alerts that started to fire during the upgrade
- Allow list of alerts that we know are relevant during upgrades? Insight severity can match alert severity.
Impact can be probably simple alertname -> impact type classifier. Message can be "Alert name: Alert message":
=Update Health= SINCE LEVEL IMPACT MESSAGE 3h Warning API Availability KubeDaemonSetRolloutStuck: DaemonSet openshift-ingress-canary/ingress-canary has not finished or progressed for at least 30 minutes.
Definition of done
- Alerts that started firing during the upgrade are shown as a upgrade health insight in upgrade health section
- Alerts that started firing before the upgrade but are present on an allowlist (hardcoded for now) of alerts relevant for update
- Create an allow list for alerts (structure) which will show the alerts in this section.
- We do not plan to decide which alerts should be in the allow list as part of this card (as this is a future card)
- blocks
-
OCPBUGS-33917 status: show upgrade-related alerts in update health section
- Closed
- is blocked by
-
OTA-1080 Proof-of-concept oc access to firing alerts
- Closed
-
OTA-1087 Add Upgrade Health section to oc adm upgrade status command
- Closed
- is cloned by
-
OCPBUGS-33917 status: show upgrade-related alerts in update health section
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update