Skip to content

OTA-740: Fix telemetry shellcheck#44591

Merged
openshift-ci[bot] merged 2 commits into
openshift:masterfrom
jupierce:fix_telemetry_shellcheck
Oct 19, 2023
Merged

OTA-740: Fix telemetry shellcheck#44591
openshift-ci[bot] merged 2 commits into
openshift:masterfrom
jupierce:fix_telemetry_shellcheck

Conversation

@jupierce
Copy link
Copy Markdown
Contributor

@jupierce jupierce commented Oct 19, 2023

#44561 for context

wking and others added 2 commits October 18, 2023 19:53
We'd tried this previously in 3c1da8e (OTA-740:
ci-operator/step-registry/ipi/conf/telemetry: Disable Telemetry
(openshift#32153), 2022-09-13), but had to roll it back with d61129c
(ci-operator/step-registry/ipi/conf/telemetry: Restore Telemetry
(openshift#32249), 2022-09-13), to avoid failing:

  Prometheus when installed on the cluster should report telemetry if a cloud.openshift.com token is present

Subsequently, openshift/origin@76652fa4fa (test/extended/prometheus:
Consider telemeterClient.enabled, 2022-09-15, openshift/origin#27422)
taught that test-case about the config knob this step uses to disable
Telemetry.  Those test-case changes are present in origin test suites
starting in 4.12:

  $ for Y in $(seq 11 15); do git --no-pager grep 'should report telemetry' "origin/release-4.${Y}" -- test/extended/prometheus/prometheus.go; done
  origin/release-4.11:test/extended/prometheus/prometheus.go:             g.It("should report telemetry if a cloud.openshift.com token is present [Late]", func() {
  origin/release-4.12:test/extended/prometheus/prometheus.go:             g.It("should report telemetry [Late]", func() {
  origin/release-4.13:test/extended/prometheus/prometheus.go:             g.It("should report telemetry [Late]", func() {
  origin/release-4.14:test/extended/prometheus/prometheus.go:             g.It("should report telemetry [Serial] [Late]", func() {
  origin/release-4.15:test/extended/prometheus/prometheus.go:             g.It("should report telemetry [Serial] [Late]", func() {

and 4.10 is end-of-life since 2023-09-10 [1].  That leaves tests using
4.11 versions of the origin suite, and I'm addressing those via the
JOB_NAME checks [2,3].  The checks are brittle, leaving out 4.9 and
earlier, and possibly not matching some 4.11 jobs, but they will
hopefully be sufficient to get us through until 4.11 goes end-of-life
on 2024-02-10 [3].  And when the defaulting logic breaks down, jobs
that have an opinion can set TELEMETRY_ENABLED explicitly to match
their needs.

[1]: https://access.redhat.com/support/policy/updates/openshift/#dates
[2]: https://docs.ci.openshift.org/docs/architecture/step-registry/#available-environment-variables
[3]: https://docs.prow.k8s.io/docs/jobs/#job-environment-variables
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 19, 2023
@openshift-ci openshift-ci Bot requested review from neisw and stbenjam October 19, 2023 13:10

if test -z "${TELEMETRY_ENABLED}"
then
if [[ "${JOB_NAME}" =~ (^|[^[:digit:]]+)4.11([^[:digit:]]+|$) ]]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok having this off on 4.12 minors and multi-upgrades too?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All relevent versions of the monitoring stack understand:

telemeterClient:
  enabled: false

The issue is whether the origin suite understands that means Telemetry has been disabled. And 4.11->4.12 update jobs are controlled by a 4.12 origin suite, so they're fine with Telemetry disabled. The current JOB_NAME matching will disable it for those jobs by default, because they mention 4.11, but 🤷, we don't need to check Telemetry in those runs, and if we decide we do, we can go for a fancier regexp or explicitly set TELEMETRY_ENABLED: "true" for those jobs.

@stbenjam
Copy link
Copy Markdown
Member

/lgtm

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jupierce: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-cluster-api-provider-aws-release-4.10-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.9-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.8-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.7-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.6-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.5-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.4-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.3-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.2-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.1-e2e-aws-operator openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-master-e2e-aws-capi-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-master-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-master-e2e-aws-ovn-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.16-e2e-aws-capi-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.16-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.16-e2e-aws-ovn-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.15-e2e-aws-capi-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.15-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.15-e2e-aws-ovn-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.14-e2e-aws-capi-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.14-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.14-e2e-aws-ovn-techpreview openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.13-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.12-e2e-aws-ovn openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.11-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.10-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.9-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.8-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.7-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.6-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.5-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.4-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.3-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.2-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed
pull-ci-openshift-cluster-api-provider-aws-release-4.1-e2e-aws openshift/cluster-api-provider-aws presubmit Registry content changed

A total of 14133 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 19, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jupierce, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse more

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-upgrade

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jupierce: job(s): periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-upgrade either don't exist or were not found to be affected, and cannot be rehearsed

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn

@jupierce
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Oct 19, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 19, 2023

@jupierce: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/file-integrity-operator/release-4.13/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.13-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.11/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.11-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.8/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.8-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.12/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.12-e2e-aws
ci/rehearse/openshift/file-integrity-operator/master/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.7/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.7-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.14/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.14-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.9/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.9-e2e-aws
ci/rehearse/openshift/file-integrity-operator/release-4.6/e2e-aws f7102a7 link unknown /pj-rehearse pull-ci-openshift-file-integrity-operator-release-4.6-e2e-aws

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-ci openshift-ci Bot merged commit 4e60e06 into openshift:master Oct 19, 2023
@wking
Copy link
Copy Markdown
Member

wking commented Oct 19, 2023

/retitle OTA-740: Fix telemetry shellcheck

@openshift-ci openshift-ci Bot changed the title Fix telemetry shellcheck OTA-740: Fix telemetry shellcheck Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants