Bug 1931594

Summary:	[sig-cli] oc --request-timeout works as expected fails frequently on s390x
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
oc sub component:	oc	QA Contact:	zhou ying <yinzhou>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, mfojtik
Version:	4.8
Target Milestone:	---
Target Release:	4.10.0
Hardware:	s390x
OS:	Unspecified
Whiteboard:	tag-ci LifecycleReset
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:	[sig-cli] oc --request-timeout works as expected
Last Closed:	2022-03-11 18:15:11 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 Adam Kaplan 2021-02-22 18:24:12 UTC

test:
[sig-cli] oc --request-timeout works as expected 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cli%5C%5D+oc+--request-timeout+works+as+expected

This appears to be failing with much higher frequency on s390x (40% pass rate on s390x vs. 100% on AWS-x86_64)

Examples with detailed failures:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-remote-libvirt-s390x-4.7/1363700169106788352

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-remote-libvirt-s390x-4.7/1363700169106788352

Failure snippets:

```
 Connection error: Get https://api.libvirt-s390x-1-3-c48ef.libvirt-s390x-1-3:6443/apis/apps.openshift.io/v1/namespaces/e2e-test-oc-request-timeout-fl5dn/deploymentconfigs/testdc?timeout=1s: context deadline exceeded
Unable to connect to the server: context deadline exceeded
```

```
Connection error: Get https://api.libvirt-s390x-0-3-c48ef.libvirt-s390x-0-3:6443/apis/apps.openshift.io/v1/namespaces/e2e-test-oc-request-timeout-zdc8s/deploymentconfigs/testdc?timeout=1s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Unable to connect to the server: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
```

Potentially related - test failures here appear to correlate with "Unauthorized" failures appearing in other failing tests.

Example:

```
Feb 21 18:35:03.047: INFO: Waiting for test-1 to complete

Feb 21 18:35:26.097: INFO: error listing builds: Unauthorized
Feb 21 18:35:26.097: INFO: WaitForABuild returning with error: Unauthorized
```

Comment 1 Maciej Szulik 2021-02-23 11:06:36 UTC

Given this is limited to only a single platform I'm lowering the priority to better reflect urgency.

Comment 2 Michal Fojtik 2021-03-25 11:20:27 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 4 Michal Fojtik 2022-01-15 08:11:48 UTC

The LifecycleStale keyword was removed because the bug got commented on recently.
The bug assignee was notified.

Comment 7 zhou ying 2022-01-25 06:34:36 UTC

Checked the recently logs , can't reproduce the issue now:

https://search.ci.openshift.org/?search=%5C%5Bsig-cli%5C%5D+oc+--request-timeout+works+as+expected&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job