test: [sig-apps][Feature:DeploymentConfig] deploymentconfigs with multiple image change triggers should run a successful deployment with multiple triggers is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-apps%5C%5D%5C%5BFeature%3ADeploymentConfig%5C%5D+deploymentconfigs+with+multiple+image+change+triggers+should+run+a+successful+deployment+with+multiple+triggers https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-ovn-4.6/1291406877116076032 Lots of reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox
This is waiting in the queue for review and merge.
Moving the bug back to assigned state as i see that the test has been failing from last 3 days when checked here [1] [1] https://search.ci.openshift.org/?search=deploymentconfigs+with+multiple+image+change+triggers+should+run+a+successful+deployment+with+multiple+triggers&maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job
From what I've checked the search results none of the failures is coming from this particular fix, but is rather coming from overall infra flakiness. See that each run has many, many more failures. Additionally, I've also merged https://github.com/openshift/origin/pull/25505 yesterday which should also improve the situation for deployments overall. Moving back to qa.
will wait till monday and check the issue before moving the bug to verified state.
Hi Maciej, I tried to verify the bug below and i do not see any errors as said in the description but i see that test is failing due to the error below, is this expected for the last two days and few other errors are related to connection errors. Basically still do not see a full pass ratio for this bug. could also you as well please help check and confirm ? Thanks !! fail [github.com/openshift/origin/test/extended/deployments/util.go:751]: watch closed unexpectedly Expected <bool>: false to be equivalent to <bool>: true
From my quick check the failures you're talking about are coming from 4.5, and I see only a handful of them so for now we're not considering backporting this. 4.6 is fixed, so this particular BZ can easily move to verified.
Thanks, got it !! Based on comment 8 , moving the bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196