[sig-cli] oc --request-timeout works as expected
is failing frequently in CI, see search results:
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:
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.
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
Given this is limited to only a single platform I'm lowering the priority to better reflect urgency.
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.
The LifecycleStale keyword was removed because the bug got commented on recently.
The bug assignee was notified.
Checked the recently logs , can't reproduce the issue now: