Bug 2103033 - CMO e2e job doesn't run any test
Summary: CMO e2e job doesn't run any test
Keywords:
Status: CLOSED DUPLICATE of bug 2100472
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.12.0
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-01 09:17 UTC by Simon Pasquier
Modified: 2022-07-06 07:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-06 07:23:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.