Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2100091

Summary:	[sig-network] pods should successfully create sandboxes
Product:	OpenShift Container Platform	Reporter:	Pablo Acevedo <pacevedo>
Component:	Test Framework	Assignee:	Pablo Acevedo <pacevedo>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.11	CC:	dgoodwin, ehila, openshift-release-oversight, rahul.sharma49
Target Milestone:	---
Target Release:	---
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:	2022-11-21 19:38:58 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 Pablo Acevedo 2022-06-22 12:21:21 UTC

Description of problem:
[sig-network] pods should successfully create sandboxes by adding pod to network
[sig-network] pods should successfully create sandboxes by getting pod
[sig-network] pods should successfully create sandboxes by writing network status

These tests fail in about 7% of runs.


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


How reproducible:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27248/pull-ci-openshift-origin-master-e2e-aws-single-node-upgrade/1539332393825996800
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27259/pull-ci-openshift-origin-master-e2e-aws-single-node-upgrade/1539228749277433856

Steps to Reproduce:


Actual results:
Test fails


Expected results:
Test pass


Additional info:

Comment 3 Rahul Sharma 2022-08-16 07:17:43 UTC

This problem is being reported in s390x architecture too


[sig-network] pods should successfully create sandboxes by getting pod 


https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-upgrade-from-nightly-4.11-ocp-remote-libvirt-s390x/1555841331840946176
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-upgrade-from-nightly-4.11-ocp-remote-libvirt-s390x/1556203724165091328
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-upgrade-from-nightly-4.11-ocp-remote-libvirt-s390x/1556566115969142784
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-upgrade-from-nightly-4.11-ocp-remote-libvirt-s390x/1556928426902818816

Comment 4 Devan Goodwin 2022-11-21 19:38:58 UTC

This test has been worked on but new reasons always pop up. Currently all tests are globally over 99%, some outliers for specific platforms on drilldown however. For purposes of this bug however I think we've cleared the problems as reported. Please open a Jira if this is still causing problems. 

https://sippy.dptools.openshift.org/sippy-ng/tests/4.13?filters=%257B%2522items%2522%253A%255B%257B%2522columnField%2522%253A%2522current_runs%2522%252C%2522operatorValue%2522%253A%2522%253E%253D%2522%252C%2522value%2522%253A%25227%2522%257D%252C%257B%2522columnField%2522%253A%2522variants%2522%252C%2522not%2522%253Atrue%252C%2522operatorValue%2522%253A%2522contains%2522%252C%2522value%2522%253A%2522never-stable%2522%257D%252C%257B%2522id%2522%253A99%252C%2522columnField%2522%253A%2522name%2522%252C%2522operatorValue%2522%253A%2522contains%2522%252C%2522value%2522%253A%2522%255Bsig-network%255D%2520pods%2520should%2520successfully%2520create%2520sandboxes%2522%257D%255D%252C%2522linkOperator%2522%253A%2522and%2522%257D&sort=asc&sortField=current_working_percentage