From 0d0ee0ebbad5f3727d409bbe631661b4c4fae07c Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Tue, 13 Sep 2022 10:16:36 -0700 Subject: [PATCH] ci-operator/config/openshift/origin/openshift-origin-master: Disable Telemetry for e2e-aws I'd disabled Telemetry for the bulk of the CI fleet in 3c1da8eb20 (OTA-740: ci-operator/step-registry/ipi/conf/telemetry: Disable Telemetry (#32153), 2022-09-13). But that lead to many failures for: Prometheus when installed on the cluster should report telemetry if a cloud.openshift.com token is present so I'd flipped the default to keeping Telemetry enabled in d61129c814 (ci-operator/step-registry/ipi/conf/telemetry: Restore Telemetry (#32249), 2022-09-13). Now I'm looking to teach the origin test-case skip about the mechanism I used to disable Telemetry, and I want an origin master presubmit with Telemetry disabled. The only run_if_changed origin master presubmits are e2e-gcp-builds, e2e-aws-jenkins, e2e-gcp-image-ecosystem, and e2e-aws-image-registry, and none of those sound like job that will run the test-case I'm interested in (although maybe they do; I haven't dug in to confirm). But e2e-aws is optional, so having the presubmit temporarily failing for other origin master pull requests won't block changes from landing. We'll revert this change and return the job to the CI-wide Telemetry default once we've confirmed that the test-case skips are smart enough. --- ci-operator/config/openshift/origin/openshift-origin-master.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci-operator/config/openshift/origin/openshift-origin-master.yaml b/ci-operator/config/openshift/origin/openshift-origin-master.yaml index bcf3d3b5ea7ea..11408d10e1913 100644 --- a/ci-operator/config/openshift/origin/openshift-origin-master.yaml +++ b/ci-operator/config/openshift/origin/openshift-origin-master.yaml @@ -91,6 +91,7 @@ tests: cluster_profile: aws-2 env: BASE_DOMAIN: aws-2.ci.openshift.org + TELEMETRY_ENABLED: "false" workflow: openshift-e2e-aws-loki - as: e2e-gcp-ovn steps: