Skip to content

[openshift-pipelines] Add presubmit e2e job for release-tests on release-v1.21 (ROSA Hypershift)#76794

Closed
anithapriyanatarajan wants to merge 1 commit into
openshift:mainfrom
anithapriyanatarajan:add-osp-e2e
Closed

[openshift-pipelines] Add presubmit e2e job for release-tests on release-v1.21 (ROSA Hypershift)#76794
anithapriyanatarajan wants to merge 1 commit into
openshift:mainfrom
anithapriyanatarajan:add-osp-e2e

Conversation

@anithapriyanatarajan
Copy link
Copy Markdown

What this PR does?

Adds a new presubmit CI job that runs the full OpenShift Pipelines e2e test suite on every PR to openshift-pipelines/release-tests targeting the release-v1.21 branch. The cluster is provisioned via the existing rosa-lifecycle-advanced workflow on ROSA HyperShift.

This is intentionally separate from the existing interop sanity jobs (openshift-pipelines-tests). No files under [tests] are modified.

New step-registry steps

e2e-tests

openshift-pipelines-e2e-tests

— runs the full gauge e2e suite (TEST_TAGS=e2e), loads cloud/registry credentials from the openshift-pipelines-e2e-credentials secret, and supports configurable spec paths via PIPELINES_TEST_SPECS.
cleanup

openshift-pipelines-cleanup

— post-test best-effort cleanup (best_effort: true) that removes PipelineRuns, PVCs, and test namespaces labelled openshift-pipelines.tekton.dev/test=true. Failures are logged but never propagate to the overall job result.

New ci-operator config

openshift-pipelines-release-tests-release-v1.21.yaml

No cron / no variant → pure presubmit, triggers on every PR.
cluster_profile: aws-sd-qe
workflow: rosa-lifecycle-advanced.
Test chain: ipi-install-rbac → cucushift-hypershift-extended-health-check → openshift-pipelines-install → openshift-pipelines-e2e-tests.
Post step: openshift-pipelines-cleanup.

Auto-generated (by make update):
openshift-pipelines-release-tests-release-v1.21-presubmits.yaml — adds job pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-e2e.

Co-authored-by: Claude

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 25, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 25, 2026

Hi @anithapriyanatarajan. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@anithapriyanatarajan
Copy link
Copy Markdown
Author

/assign @srivickynesh

Signed-off-by: Anitha Natarajan <anataraj@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 25, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anithapriyanatarajan
Once this PR has been reviewed and has the lgtm label, please ask for approval from srivickynesh and additionally assign etirta for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@anithapriyanatarajan: 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-pipelines-release-tests-release-v1.21-images openshift-pipelines/release-tests presubmit Presubmit changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-e2e openshift-pipelines/release-tests presubmit Presubmit changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-ocp-4.22-lp-interop-images openshift-pipelines/release-tests presubmit Ci-operator config changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp-4.21-lp-interop-cr-images openshift-pipelines/release-tests presubmit Ci-operator config changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp-4.21-lp-interop-images openshift-pipelines/release-tests presubmit Ci-operator config changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.20-lp-rosa-hypershift-images openshift-pipelines/release-tests presubmit Ci-operator config changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.21-e2e-osp-images openshift-pipelines/release-tests presubmit Ci-operator config changed
pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.21-lp-rosa-hypershift-images openshift-pipelines/release-tests presubmit Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.21-e2e-osp-openshift-pipelines-e2e-osp N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.21-lp-rosa-hypershift-openshift-pipelines-aws-rosa-hypershift N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-ocp-4.22-lp-interop-cr-openshift-pipelines-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-ocp-4.22-lp-interop-openshift-pipelines-aws-fips N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp-4.21-lp-interop-cr-openshift-pipelines-interop-aws N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp-4.21-lp-interop-openshift-pipelines-interop-aws-fips N/A periodic Ci-operator config changed
periodic-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-ocp4.20-lp-rosa-hypershift-openshift-pipelines-aws-rosa-hypershift N/A periodic 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.

@anithapriyanatarajan
Copy link
Copy Markdown
Author

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@anithapriyanatarajan: needs-ok-to-test label found, no rehearsals will be run

@anithapriyanatarajan anithapriyanatarajan marked this pull request as draft March 25, 2026 08:38
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 25, 2026
@vdemeester
Copy link
Copy Markdown
Member

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 25, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Author

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 25, 2026

@anithapriyanatarajan: 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-pipelines/release-tests/release-v1.21/openshift-pipelines-e2e ebde185 link unknown /pj-rehearse pull-ci-openshift-pipelines-release-tests-release-v1.21-openshift-pipelines-e2e
ci/rehearse/periodic-ci-openshift-pipelines-release-tests-release-v1.21-ocp-4.22-lp-interop-cr-openshift-pipelines-aws ebde185 link unknown /pj-rehearse periodic-ci-openshift-pipelines-release-tests-release-v1.21-ocp-4.22-lp-interop-cr-openshift-pipelines-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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 28, 2026

PR needs rebase.

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Author

closing this in favor of #79867

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants