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
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary