Skip to content
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

[hypershift-rosa] remove hypershfit rosa 4.12 ci jobs and move them to 4.13 ci #43003

Merged

Conversation

heliubj18
Copy link
Contributor

remove hypershfit rosa 4.12 ci jobs and move them to 4.13 ci

@heliubj18
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@heliubj18: 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
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-nightly-aws-rosa-sts-hypershift-guest-f7 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-stable-aws-rosa-sts-hypershift-guest-integration-full-f7 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-stable-aws-rosa-sts-hypershift-guest-stage-critical-f2 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-stable-aws-rosa-sts-hypershift-guest-integration-critical-f2 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-stable-aws-rosa-sts-hypershift-sector-guest-prod-critical-f2 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-stable-aws-rosa-sts-hypershift-guest-stage-full-f7 N/A periodic Periodic changed
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.

@heliubj18
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-nightly-aws-rosa-sts-hypershift-guest-f7

@LiangquanLi930
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 6, 2023
@heliubj18
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Sep 6, 2023
@heliubj18
Copy link
Contributor Author

@liangxia Could you please help to review this PR? thanks

@@ -177,6 +177,82 @@ tests:
test:
- chain: openshift-e2e-test-qe
workflow: rosa-aws-sts
- as: aws-rosa-sts-hypershift-guest-integration-critical-f2
Copy link
Member

Choose a reason for hiding this comment

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

The aws-rosa-sts-hypershift-guest-integration-full-f7 takes about two hours for the e2e to finish. So there is no need to keep the critical test now, as it has been well covered by the full test.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is used to verify HO rosa upgrade release process. It is like the gating test, we must make sure all cases are passed now. So we can not use full cases to run in this process because there are a lot of failures that can not determine whether to continue the upgrade process.

@liangxia
Copy link
Member

liangxia commented Sep 6, 2023

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 6, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: heliubj18, LiangquanLi930, liangxia

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 Sep 6, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 6, 2023

@heliubj18: 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/periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-nightly-aws-rosa-sts-hypershift-guest-f7 8e818d1 link unknown /pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.13-amd64-nightly-aws-rosa-sts-hypershift-guest-f7

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

@openshift-merge-robot openshift-merge-robot merged commit 81d4583 into openshift:master Sep 6, 2023
prb112 pushed a commit to prb112/openshift-release that referenced this pull request Sep 12, 2023
…o 4.13 ci (openshift#43003)

* remove 4.12 rosa hypershift ci jobs and move them to 4.13 ci

* add report
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.

5 participants