Bug 2066457
| Summary: | Prometheus CI failure: 503 Service Unavailable | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | mkenigsb |
| Component: | Monitoring | Assignee: | Simon Pasquier <spasquie> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.11 | CC: | amuller, anpicker, sthaha, walters |
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 10:55:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2077516 | ||
@mkenigsb Please re-assign the bug to the responsible team. Thank you. This is causing a quite high flake rate across certain job types. Look at this query: https://search.ci.openshift.org/?search=Prometheus%3A+request+failed+with+code+503+Service+Unavailable%3B&maxAge=168h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Specifically e.g. periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-azure-ovn-upgrade (all) - 7 runs, 100% failed, 43% of failures match = 43% impact https://prow.ci.openshift.org/job-history/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-azure-ovn-upgrade I can't speak to where this should fall in the team priority list but I think it's higher than "low". Increasing priority on this one since it may be a regression in the Thanos sidecar reporting ready while it isn't. since the issue is fixed in 4.11, searched with https://search.ci.openshift.org/?search=Prometheus%3A+request+failed+with+code+503+Service+Unavailable%3B&maxAge=48h&context=1&type=bug%2Bjunit&name=4.11.*&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job no error logs for 4.11, move to VERIFIED 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 |
Description of problem: e2e-agnostic-upgrade failed with: { fail [github.com/openshift/origin/test/e2e/upgrade/alert/alert.go:212]: unable to check firing alerts during upgrade Unexpected error: <errors.aggregate | len:1, cap:1>: [ { s: "receive series from Addr: 10.128.2.13:10901 LabelSets: Mint: -62167219200000 Maxt: 9223372036854775807: rpc error: code = Unknown desc = query Prometheus: request failed with code 503 Service Unavailable; msg Service Unavailable", }, ] receive series from Addr: 10.128.2.13:10901 LabelSets: Mint: -62167219200000 Maxt: 9223372036854775807: rpc error: code = Unknown desc = query Prometheus: request failed with code 503 Service Unavailable; msg Service Unavailable occurred} Prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/3023/pull-ci-openshift-machine-config-operator-master-e2e-agnostic-upgrade/1504883685273374720 How reproducible: Looked on search.ci.openshift.org and it looks like there have been quite a few failures with the same error