Description of problem: In CI, upgrade e2e jobs fails in the test named "[sig-network] pods should successfully create sandboxes by other". please, refer to the following search to see all the related test failures: https://search.ci.openshift.org/?search=pods+should+successfully+create+sandboxes+by+other&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Version-Release number of selected component (if applicable): upgrade 4.7 to 4.8 How reproducible: Notice it on recent upgrade jobs in CI for s390x https://prow.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-upgrade-remote-libvirt-s390x-4.7-to-4.8 Steps to Reproduce: please, refer above Actual results: the test fails. Expected results: the test should either pass or be disabled. Additional info:
This testcase is also failing in ppc64le upgrade (4.7 to 4.8) environment.
Jamo, I think this is related to one of the subsidiary bugs of https://bugzilla.redhat.com/show_bug.cgi?id=1943566 Can you please take a look and see if it is a duplciate, or something novel? Thanks
Hi, do we have updates on this? as the test case to continuously fails in the upgrade CI jobs for s390x. https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/release-openshift-ocp-installer-upgrade-remote-libvirt-s390x-4.7-to-4.8 https://search.ci.openshift.org/?search=pods+should+successfully+create+sandboxes+by+other&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
(In reply to Ben Bennett from comment #3) > Jamo, I think this is related to one of the subsidiary bugs of > https://bugzilla.redhat.com/show_bug.cgi?id=1943566 > > Can you please take a look and see if it is a duplciate, or something novel? > Thanks No real update on my side, but I think we might want to dup this and https://bugzilla.redhat.com/show_bug.cgi?id=1978090 There is a PR that could help assigned to 1978090 (https://github.com/openshift/origin/pull/26297) that we can hopefully wait for and see where we stand with this.
I hadn't looked at this in a while, but recently I was debugging some failing upgrade jobs and filed a new bug around this. Let me dup this to that one as I'm attempting to get to the bottom of it and that's the only "[sig-network] pods should successfully create sandboxes by other" failure I see right now. *** This bug has been marked as a duplicate of bug 2038481 ***