Bug 2091067

Summary: EgressIP tests occasionally hit: dial tcp 192.168.83.2:6443: i/o timeout
Product: OpenShift Container Platform Reporter: Andreas Karis <akaris>
Component: Test FrameworkAssignee: Andreas Karis <akaris>
Status: VERIFIED --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 4.11CC: openshift-release-oversight
Target Milestone: ---   
Target Release: 4.11.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: 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 Andreas Karis 2022-05-27 13:42:34 UTC 
Description of problem:
EgressIP tests occasionally hit: dial tcp 192.168.83.2:6443: i/o timeout

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Retry on those timeouts the same as kubectl kubectlExecWithRetry


Additional info:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-vsphere-serial/1530096657255895040

 [sig-network][Feature:EgressIP] [external-targets] pods should keep the assigned EgressIPs when being rescheduled to another node [Serial] [Suite:openshift/conformance/serial] expand_less 	32s
{  fail [github.com/openshift/origin/test/extended/util/client.go:209]: May 27 10:00:12.918: Get "https://api.ci-op-6wfgz6vx-a9bd0.vmc-ci.devcluster.openshift.com:6443/apis/user.openshift.io/v1/users/~": dial tcp 192.168.83.2:6443: i/o timeout}
open stdoutopen_in_new