Skip to content

OCPCLOUD-2917: test rebases with e2e-tests on aws #65068

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

miyadav
Copy link
Member

@miyadav miyadav commented May 19, 2025

e2e qe tests for cluster-api repo

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 19, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 19, 2025

@miyadav: This pull request references OCPCLOUD-2917 which is a valid jira issue.

In response to this:

e2e qe tests for cluster-api repo

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@miyadav: 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-master-e2e-aws-capi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-aws-ovn openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-aws-ovn-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-aws-serial-1of2 openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-aws-serial-2of2 openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-azure-capi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-gcp-capi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-hypershift openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-openstack-capi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-e2e-vsphere-capi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-images openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-okd-scos-e2e-aws-ovn openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-okd-scos-images openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-regression-clusterinfra-aws-ipi-techpreview openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-unit openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-verify-commits openshift/cluster-api presubmit Ci-operator config changed
pull-ci-openshift-cluster-api-master-verify-deps openshift/cluster-api presubmit Ci-operator config changed

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

@miyadav
Copy link
Member Author

miyadav commented May 19, 2025

/pj-rehearse pull-ci-openshift-cluster-api-master-regression-clusterinfra-aws-ipi-techpreview

@openshift-ci-robot
Copy link
Contributor

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

Copy link
Contributor

openshift-ci bot commented May 19, 2025

@miyadav: The following test 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/cluster-api/master/regression-clusterinfra-aws-ipi-techpreview 7ef0041 link unknown /pj-rehearse pull-ci-openshift-cluster-api-master-regression-clusterinfra-aws-ipi-techpreview

Full PR test history. Your PR dashboard.

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.

@miyadav
Copy link
Member Author

miyadav commented May 21, 2025

@JoelSpeed @sunzhaohua2 , do we consider merging this , to increase the number of tests to run on pre-submits ?
we can add verification-tests image ( i think i missed in this to let those run as well )

@JoelSpeed
Copy link
Contributor

/lgtm
/approve

Happy to merge if you're happy with the result?

There is one failure? Is that known? A flake?

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
Copy link
Contributor

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, miyadav

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

The pull request process is described here

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 21, 2025
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants