Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-6787

Missing runbook for the KubeDaemonSetMisScheduled alert

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Normal
    • None
    • 4.12
    • Monitoring
    • None
    • Moderate
    • MON Sprint 243, MON Sprint 244
    • 2
    • False
    • Hide

      None

      Show
      None

    Description

      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/

       

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-18831 Missing runbook for the KubeDaemonSetRolloutStuck alert

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • ASSIGNED
          is documented by

          Task - Represents a small unit of work that is not end-user facing. OBSDOCS-496 Edit content for new KubeDaemonSetMisScheduled runbook

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              janantha@redhat.com Jayapriya Pai
              spasquie@redhat.com Simon Pasquier
              Tai Gao Tai Gao
              Simon Pasquier
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: