Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2516

[4.22] alert/KubePodNotReady should not be at or above info in ns/default

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.22
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This doesn't happen all the time but it's been enough to fail two payloads so far.
      slack thread
      example

      [Monitor:legacy-test-framework-invariants-alerts][Unknown][invariant] alert/KubePodNotReady should not be at or above info in ns/default
{  KubePodNotReady was at or above info for at least 7m42s on platformidentification.JobType{Release:"4.22", FromRelease:"4.21", Platform:"aws", Architecture:"amd64", Network:"ovn", Topology:"ha"} (maxAllowed=0s): pending for 0s, firing for 7m42s:
Jan 20 12:03:04.535 - 462s  W namespace/default pod/verify-all-openshiftredhatmarketplace-vlmkp-cwp6l alert/KubePodNotReady alertstate/firing severity/warning ALERTS{alertname="KubePodNotReady", alertstate="firing", namespace="default", pod="verify-all-openshiftredhatmarketplace-vlmkp-cwp6l", prometheus="openshift-monitoring/k8s", severity="warning"}}

       

              Unassigned Unassigned
              lmeyer@redhat.com Luke Meyer
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: