Bug 2091067 - EgressIP tests occasionally hit: dial tcp 192.168.83.2:6443: i/o timeout
Summary: EgressIP tests occasionally hit: dial tcp 192.168.83.2:6443: i/o timeout
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Framework
Version: 4.11
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.11.0
Assignee: Andreas Karis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-27 13:42 UTC by Andreas Karis
Modified: 2024-04-30 18:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-30 18:04:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27185 0 None open Bug 2091067: EgressIP: Make tests retry on API timeout errors 2022-05-27 14:05:11 UTC

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

Comment 2 Rory Thrasher 2024-04-30 18:04:53 UTC
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


Note You need to log in before you can comment on or make changes to this bug.