-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.12
-
Moderate
-
None
-
MON Sprint 243, MON Sprint 244
-
2
-
False
-
Description of problem:
When KubeDaemonSetMisScheduled alert fire, it's not obvious for cluster admins to understand why the alert happen, what is the impact and how to fix them.
Version-Release number of selected component (if applicable):
4.12 (and earlier)
How reproducible:
Steps to Reproduce:
1. KubeDaemonSetMisScheduled alert is firing. 2. 3.
Actual results:
No "runbook_url" annotation in the alert.
Expected results:
"runbook_url" annotation present.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1814723 https://redhat-internal.slack.com/archives/C0VMT03S5/p1674837317668709 https://blog.florentdelannoy.com/blog/2020/kube-daemonset-misscheduled/
- is cloned by
-
OCPBUGS-18831 Missing runbook for the KubeDaemonSetRolloutStuck alert
- ASSIGNED
- is documented by
-
OBSDOCS-496 Edit content for new KubeDaemonSetMisScheduled runbook
- Closed