-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.12.z
-
-
-
Moderate
-
No
-
MON Sprint 243
-
1
-
False
-
Description of problem:
alert TelemeterClientFailures fired for 1020 seconds with labels: {namespace="openshift-monitoring", severity="warning"} which are causing failures in periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-upgrade-rollback-oldest-supported job. For periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-upgrade-rollback-oldest-supported (all) - 26 runs, 31% failed, 38% of failures match = 12% impact
Also observed the alert fired in other upgrade ci jobs. https://search.ci.openshift.org/?search=alert+TelemeterClientFailures+fired&maxAge=336h&context=1&type=junit&name=periodic.*4.12.*-upgrade&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
Failed job link is here https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-upgrade-rollback-oldest-supported/1708850967279046656
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Flaky
Steps to Reproduce:
1. 2. 3.
Actual results:
alert TelemeterClientFailures fired in the disruption_tests: [sig-arch] Check if alerts are firing during or after upgrade success
Expected results:
No alert fired
Additional info:
