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

alert/OVNKubernetesResourceRetryFailure

XMLWordPrintable

    • Icon: Ticket Ticket
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Two payloads failed with examples of the same error:

      [Monitor:legacy-test-framework-invariants-alerts][bz-networking][invariant] alert/OVNKubernetesResourceRetryFailure should not be at or above info
      
      {  OVNKubernetesResourceRetryFailure was at or above info for at least 9m28s on platformidentification.JobType{Release:"4.22", FromRelease:"4.21", Platform:"azure", Architecture:"amd64", Network:"ovn", Topology:"ha"} (maxAllowed=0s): pending for 0s, firing for 9m28s:
      
      Jan 21 17:23:56.950 - 568s  W namespace/openshift-ovn-kubernetes node/10.0.128.5:9103 pod/ovnkube-node-68xtz container/kube-rbac-proxy-node alert/OVNKubernetesResourceRetryFailure alertstate/firing severity/warning ALERTS{alertname="OVNKubernetesResourceRetryFailure", alertstate="firing", container="kube-rbac-proxy-node", endpoint="metrics", instance="10.0.128.5:9103", job="ovnkube-node", namespace="openshift-ovn-kubernetes", pod="ovnkube-node-68xtz", prometheus="openshift-monitoring/k8s", service="ovn-kubernetes-node", severity="warning"}}

      4.22.0-0.ci-2026-01-21-020418 failed inĀ aggregated-gcp-ovn-upgrade-4.22-micro

      4.22.0-0.ci-2026-01-21-080418 failed in aggregated-azure-ovn-upgrade-4.22-minor

      4.22.0-0.ci-2026-01-21-140419 passed but periodic-ci-openshift-release-master-ci-4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade did fail twice (#2013976877512790016 #2013976867438071808) so it's still out there.

      Nothing obvious (to me) causing it.

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

                Created:
                Updated:
                Resolved: