Bug 1983758
Summary: | upgrades are failing on disruptive tests | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Stephen Benjamin <stbenjam> |
Component: | Networking | Assignee: | Chad Scribner <cscribne> |
Networking sub component: | router | QA Contact: | Melvin Joseph <mjoseph> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | amcdermo, aos-bugs, bmcelvee, cholman, cscribne, ggiguash, hongli, mmasters, wking |
Version: | 4.9 | Keywords: | Reopened |
Target Milestone: | --- | ||
Target Release: | 4.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
[sig-network-edge] Cluster frontend ingress remain available
[sig-api-machinery] OpenShift APIs remain available for new connections
[sig-api-machinery] OAuth APIs remain available for new connections
[sig-api-machinery] OAuth APIs remain available with reused connections 84.783 -10.79 95.573
[sig-api-machinery] OpenShift APIs remain available with reused connections
[sig-api-machinery] Kubernetes APIs remain available with reused connections 84.647 -10.62 95.267
[sig-api-machinery] Kubernetes APIs remain available for new connections
job=periodic-ci-openshift-release-master-ci-4.9-e2e-gcp-upgrade=all
job=periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-gcp-upgrade=all
job=periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-gcp-ovn-upgrade=all
|
|
Last Closed: | 2022-03-12 04:36:01 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: |
Description
Stephen Benjamin
2021-07-19 17:08:10 UTC
Last time it fixed itself after a few days, but starting on 8/22, we're seeing it again on both 4.8 and 4.9 gcp upgrades: e.g.: https://sippy.ci.openshift.org/sippy-ng/tests/4.9/analysis?test=[sig-api-machinery]%20Kubernetes%20APIs%20remain%20available%20with%20reused%20connections https://sippy.ci.openshift.org/sippy-ng/tests/4.8/analysis?test=[sig-api-machinery]%20Kubernetes%20APIs%20remain%20available%20with%20reused%20connections Given this has happened twice now, both times we've found no commits that are possible culprits, it's only GCP, and it's happening on two releases at the exact same time, I think it's unlikely related to code changes on our side. Is it possible to get logging from LB's on GCP? Or escalate this to their support? The issues appear to be for more than just gcp this time: https://sippy.ci.openshift.org/sippy-ng/tests/4.9/analysis?test=[sig-api-machinery]%20Kubernetes%20APIs%20remain%20available%20with%20reused%20connections Hi Stephen -- I've picked up this BZ. Would you mind confirming if this issue is still occurring? If it is, are the links you posted previously still the right place to check to get the overall picture of the failures/flakes? Hi Chad! I think we can close this -- ultimately we determined the cause was the CI cluster in use. The PR for this bug is merged to 4.10.0-0.ci-2021-12-18-095230. From this CI job, it is evident the issue is no longer recurring. https://prow.ci.openshift.org/pr-history/?org=openshift&repo=origin&pr=26699 So marking the bug as verified Hi, if there is anything that customers should know about this bug or if there are any important workarounds that should be outlined in the bug fixes section OpenShift Container Platform 4.10 release notes, please update the Doc Type and Doc Text fields. If not, can you please mark it as "no doc update"? Thanks! 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 (Moderate: OpenShift Container Platform 4.10.3 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:0056 |