Description of problem: Able to create CSV of same name Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-04-03-093209 4.4.0-0.nightly-2020-04-03-072527 How reproducible: Sometimes Steps to Reproduce: 1. Check release-openshift-ocp-installer-e2e-gcp-ovn-4.4 runs 2. Look for "Marketplace diff name test" 3. Find test results Actual results: [Feature:Marketplace] Marketplace diff name test [Top Level] [Feature:Marketplace] Marketplace diff name test [ocp-25672] create the samename opsrc&csc [Suite:openshift/conformance/parallel] expand_less 36s fail [github.com/openshift/origin/test/extended/marketplace/marketplace_diffname.go:84]: Expected <string>: to contain substring <string>: Deployment samename exists Expected results: Expected to see "Deployment samename exists" Additional info:
this is failing 15% of the time it runs, raising severity and please backport any fix to 4.4 so we can have clean runs there as well.
This seems to be an issue with the test asking too quickly - a suggested fix https://github.com/openshift/openshift-tests/pull/30
https://github.com/openshift/openshift-tests/pull/30 is merged, and I don't see the original test as a flake on the gcp-ovn 4.4 suite.
This bug is ON_QA despite linking [1] (which is in need of a rebase and hasn't been touched in 2 weeks), but it still fails in 3% of 4.4 release jobs [2]. Does [1] need to get revived or something? [1]: https://github.com/openshift/origin/pull/24871 [2]: https://search.apps.build01.ci.devcluster.openshift.com/chart?name=release-openshift-ocp.*4.4&search=failed:.*Marketplace%20diff%20name%20test.*create%20the%20samename%20opsrc&maxAge=24h
The fix for origin :https://github.com/openshift/origin/pull/24986
https://search.apps.build01.ci.devcluster.openshift.com/chart?name=release-openshift-ocp.*4.4&search=failed:.*Marketplace%20diff%20name%20test.*create%20the%20samename%20opsrc&maxAge=24h No failed of this test case in recently 24 hours. Verified this bug.
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, 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:2871