Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1810480

Summary: [Disruptive] Cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade] test is failing 5/7 attempts
Product: OpenShift Container Platform Reporter: Vadim Rutkovsky <vrutkovs>
Component: kube-apiserverAssignee: Abu Kashem <akashem>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: akashem, aos-bugs, lmohanty, mfojtik
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-06 23:44:55 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 Vadim Rutkovsky 2020-03-05 10:46:35 UTC 
Description of problem:
Update tests for 4.1.37 are failing often (7/10 attempts, 70%) on "[Disruptive] Cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade]" test.

See https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/20056/build-log.txt for sample log

Previous 4.1.z releases:

* https://openshift-release.svc.ci.openshift.org/releasestream/4-stable/release/4.1.34 ( 26 upgrades / 15 failures on distruptive tests = 57%)
Comment 1 Vadim Rutkovsky 2020-03-05 10:53:16 UTC 
Mar 05 09:51:48.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Mar 05 09:51:54.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Mar 05 09:52:01.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: context deadline exceeded
Mar 05 09:52:07.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Mar 05 09:52:12.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Mar 05 09:52:17.125 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Mar 05 09:55:43.132 E kube-apiserver Kube API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/kube-system?timeout=3s: unexpected EOF
Mar 05 09:55:43.132 I openshift-apiserver OpenShift API started failing: Get https://api.ci-op-gbz7tdm6-77109.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift-apiserver/imagestreams/missing?timeout=3s: unexpected EOF
Comment 2 Lalatendu Mohanty 2020-03-05 11:16:20 UTC 
I also see errors mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1734524 in the log
Comment 4 Abu Kashem 2020-04-06 23:44:55 UTC 

*** This bug has been marked as a duplicate of bug 1821495 ***