Bug 2103033

Summary:	CMO e2e job doesn't run any test
Product:	OpenShift Container Platform	Reporter:	Simon Pasquier <spasquie>
Component:	Monitoring	Assignee:	Simon Pasquier <spasquie>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.11	CC:	amuller, anpicker
Target Milestone:	---
Target Release:	4.12.0
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-07-06 07:23: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 Simon Pasquier 2022-07-01 09:17:36 UTC

Description of problem:
Since [1], the CMO repository stopped running the operator e2e tests.

[1] https://github.com/openshift/cluster-monitoring-operator/commit/93bf177968bad97ac64839b2f48f03199d262f68

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

How reproducible:
Always

Steps to Reproduce:
1. Check the test log from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-monitoring-operator/1701/pull-ci-openshift-cluster-monitoring-operator-master-e2e-agnostic-operator/1541760013813420032
2. 
3.

Actual results:
Some tests are executed

Expected results:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-monitoring-operator/1701/pull-ci-openshift-cluster-monitoring-operator-master-e2e-agnostic-operator/1541760013813420032/artifacts/e2e-agnostic-operator/test/build-log.txt says:

testing: warning: no tests to run
PASS
ok  	github.com/openshift/cluster-monitoring-operator/test/e2e	12.397s [no tests to run]

Additional info:

Comment 1 Simon Pasquier 2022-07-05 12:01:50 UTC

The bug only affects the CMO end-to-end tests so not a blocker.

Comment 3 Simon Pasquier 2022-07-06 07:23:58 UTC

it has been fixed along with bug 2100472.

*** This bug has been marked as a duplicate of bug 2100472 ***