Skip to content

[Debug] Add wait step to opentelemetry-upstream-tests for OCP 4.22#79386

Open
IshwarKanse wants to merge 2 commits into
openshift:mainfrom
IshwarKanse:debug-opentelemetry-upstream-tests-4.22-20260518
Open

[Debug] Add wait step to opentelemetry-upstream-tests for OCP 4.22#79386
IshwarKanse wants to merge 2 commits into
openshift:mainfrom
IshwarKanse:debug-opentelemetry-upstream-tests-4.22-20260518

Conversation

@IshwarKanse
Copy link
Copy Markdown
Member

@IshwarKanse IshwarKanse commented May 18, 2026

Summary

  • Replaces distributed-tracing-tests-opentelemetry-upstream ref with wait step for debugging
  • Job: pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.22-amd64-opentelemetry-upstream-tests
  • Timeout: 10 hours (TIMEOUT: +10 hours)

The wait step pauses the job before tests run, allowing SSH access to:

  • Inspect system state and logs
  • Debug configuration issues
  • Investigate test failures

⚠️ DO NOT MERGE — close this PR after debugging is complete.

This PR modifies the OpenShift CI configuration for the open-telemetry/opentelemetry-operator repository to add a temporary debug pause and a longer timeout to the upstream OCP 4.22 test job.

What changed (practical effect)

  • Affects the upstream CI job that runs opentelemetry-operator tests on OCP 4.22 (the job triggered from ci-operator config: openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64).
  • Increases the test step runtime allowance by setting TIMEOUT: +10 hours so the job will not time out quickly during debugging.
  • Replaces the downstream test reference with a ref: wait step before tests run. This pauses the job (allowing SSH into the test cluster) so developers can inspect system state and logs, debug configuration, and investigate test failures interactively.

Notes

  • This is a debug-only change (marked DO NOT MERGE) and is intended to be temporary; the PR should be closed/removed once debugging is complete.

Replaces distributed-tracing-tests-opentelemetry-upstream with wait step
to enable SSH access for debugging test failures. TIMEOUT set to 10 hours.

OCP Version: 4.22
Job: pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.22-amd64-opentelemetry-upstream-tests

DO NOT MERGE — close this PR after debugging is complete.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 18, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: fb0ac275-55c2-457d-9b67-0ab7715344cf

📥 Commits

Reviewing files that changed from the base of the PR and between 37a399a and 1365b84.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml
✅ Files skipped from review due to trivial changes (1)
  • ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml

Hidden review stack artifact

Walkthrough

This PR updates an OpenShift CI workflow for the OpenTelemetry operator: it adds a TIMEOUT: +10 hours environment variable to the upstream tests step and changes a downstream step ref to wait.

Changes

OpenTelemetry Upstream Test Workflow Configuration

Layer / File(s) Summary
Upstream test timeout and workflow step updates
ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml
Adds TIMEOUT: +10 hours to the upstream tests step environment (line 121) and updates the subsequent step ref from distributed-tracing-tests-opentelemetry-upstream to wait (line 139).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • jgbernalp
  • pavolloffay
🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main changes: adding a wait step and timeout adjustment for OpenTelemetry upstream tests on OCP 4.22.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed This PR modifies only CI workflow configuration YAML files, not Ginkgo test code. The custom check applies to Ginkgo tests, which are not present in modified files.
Test Structure And Quality ✅ Passed This PR only modifies OpenShift CI workflow configuration (YAML), not Ginkgo test code. The check targets test code quality patterns and is not applicable here.
Microshift Test Compatibility ✅ Passed This PR modifies CI workflow configuration only (YAML file), not adding new Ginkgo e2e tests. The MicroShift Test Compatibility check only applies to new test code.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR only modifies a YAML CI configuration file. No new Ginkgo e2e tests (It(), Describe(), Context(), When()) are added. The SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed This PR modifies a CI/CD workflow config file, not deployment manifests, operator code, or controllers. The check applies only to the latter. No scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR modifies only OpenShift CI workflow YAML configuration, not source code. The OTE Binary Stdout Contract check is for source code stdout violations and is not applicable to CI configuration files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies a CI workflow configuration file, not Ginkgo e2e tests. The custom check explicitly applies to new Ginkgo e2e tests. No test code was added or modified.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 18, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IshwarKanse

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 18, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml`:
- Line 141: The lane currently uses a placeholder ref ("ref: wait") which
replaces the real upstream test and can accidentally mark
opentelemetry-upstream-tests as green; restore a hard guard by either (A) adding
an intentional failure step after the wait (e.g., a terminating `fail` or `exit
1` equivalent) so the debug lane cannot be mistaken for a passing test, or (B)
isolate the debug lane by renaming it to a clearly temporary name (for example
prefix/suffix like "debug-...-TEMP" or "wip-...-DO-NOT-MERGE") and ensure it is
not referenced by gating/validation rules; target the entry that currently
contains the "ref: wait" and the lane id "opentelemetry-upstream-tests" when
making the change.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 574bd66c-4cdf-469a-9390-cacc81c69c87

📥 Commits

Reviewing files that changed from the base of the PR and between 6cf3509 and 37a399a.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml

memory: 400Mi
- ref: install-operators
- ref: distributed-tracing-tests-opentelemetry-upstream
- ref: wait
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Avoid accidental false-green by replacing test execution with wait.

This change removes the actual upstream test ref from the lane, so a merge would turn opentelemetry-upstream-tests into a debug wait job instead of a validation signal. Please add a hard guard (for example, make the debug lane fail intentionally after wait or isolate it under a clearly temporary test name) to prevent accidental merge impact.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/open-telemetry-opentelemetry-operator/openshift-open-telemetry-opentelemetry-operator-main__upstream-ocp-4.22-amd64.yaml`
at line 141, The lane currently uses a placeholder ref ("ref: wait") which
replaces the real upstream test and can accidentally mark
opentelemetry-upstream-tests as green; restore a hard guard by either (A) adding
an intentional failure step after the wait (e.g., a terminating `fail` or `exit
1` equivalent) so the debug lane cannot be mistaken for a passing test, or (B)
isolate the debug lane by renaming it to a clearly temporary name (for example
prefix/suffix like "debug-...-TEMP" or "wip-...-DO-NOT-MERGE") and ensure it is
not referenced by gating/validation rules; target the entry that currently
contains the "ref: wait" and the lane id "opentelemetry-upstream-tests" when
making the change.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@IshwarKanse: 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-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.22-amd64-opentelemetry-upstream-tests openshift/open-telemetry-opentelemetry-operator presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 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 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 18, 2026

@IshwarKanse: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

@IshwarKanse
Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-open-telemetry-opentelemetry-operator-main-upstream-ocp-4.22-amd64-opentelemetry-upstream-tests

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@IshwarKanse: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant