Bug 2084288 - "alert/Watchdog must have no gaps or changes" failing after bump
Summary: "alert/Watchdog must have no gaps or changes" failing after bump
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.11.0
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-11 19:33 UTC by Stephen Benjamin
Modified: 2022-08-10 11:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:11:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift prometheus-operator pull 177 0 None open Bug 2084288: Revert "Bump openshift/prometheus-operator to v0.56.2" 2022-05-12 12:10:10 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:11:45 UTC

Description Stephen Benjamin 2022-05-11 19:33:08 UTC
In the first release payload after merging the most recent attempt, we failed 2 out of 10 runs with "watchdog much have no gaps or changes" -- and the failures includes tens of thousands of changes. This test historically passes at close to 100%, so dropping down to 80% is pretty drastic.

> Watchdog alert had 23923 changes during the run

From https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-upgrade/1524417193415020544

Aggregated run:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregated-gcp-sdn-upgrade-4.11-micro-release-openshift-release-analysis-aggregator/1524417201858154496

Comment 6 errata-xmlrpc 2022-08-10 11:11:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069


Note You need to log in before you can comment on or make changes to this bug.