Skip to content

MCO-1652: Add new MCO disruptive suite #29800

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 23, 2025
Merged

MCO-1652: Add new MCO disruptive suite #29800

merged 1 commit into from
May 23, 2025

Conversation

yuqi-zhang
Copy link
Contributor

Add an empty MCO suite, for testing purposes. Future tests will be moved over from serial and added via MCO OTE.

Alternative to #29776

@yuqi-zhang
Add new MCO disruptive suite
d408adb 
Add an empty MCO suite, for testing purposes. Future tests will be moved
over from serial and added via MCO OTE.
@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial May 15, 2025 23:33
@djoshy
Copy link
Contributor

djoshy commented May 16, 2025

/lgtm from MCO POV!

isabella-janssen
isabella-janssen reviewed May 19, 2025
View reviewed changes
Copy link
Member

@isabella-janssen isabella-janssen left a comment

Choose a reason for hiding this comment

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

lgtm too!

@neisw
Copy link
Contributor

neisw commented May 21, 2025

/lgtm

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

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, neisw, yuqi-zhang

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
@yuqi-zhang yuqi-zhang changed the title Add new MCO disruptive suite MCO-1652: Add new MCO disruptive suite May 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 21, 2025 •
edited by openshift-ci bot
Loading

@yuqi-zhang: This pull request references MCO-1652 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Add an empty MCO suite, for testing purposes. Future tests will be moved over from serial and added via MCO OTE.

Alternative to #29776

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 21, 2025
@yuqi-zhang
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9fe26ce and 2 for PR HEAD d408adb in total

@openshift-trt openshift-trt
Copy link

openshift-trt bot commented May 21, 2025

Job Failure Risk Analysis for sha: d408adb

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade IncompleteTests
Tests for this run (19) are below the historical average (1332): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 89f0d61 and 2 for PR HEAD d408adb in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 22, 2025 •
edited
Loading

@yuqi-zhang: 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/prow/e2e-openstack-serial d408adb link false /test e2e-openstack-serial
ci/prow/e2e-aws-ovn-kube-apiserver-rollout d408adb link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-rt-upgrade d408adb link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 d408adb link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-gcp-disruptive d408adb link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-serial-publicnet d408adb link false /test e2e-aws-ovn-serial-publicnet
ci/prow/e2e-aws-ovn-single-node-serial d408adb link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-serial d408adb link false /test e2e-metal-ipi-serial
ci/prow/e2e-azure-ovn-etcd-scaling d408adb link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node-upgrade d408adb link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-etcd-scaling d408adb link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback d408adb link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-azure-ovn-upgrade d408adb link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-fips-serial d408adb link false /test e2e-gcp-fips-serial
ci/prow/okd-e2e-gcp d408adb link false /test okd-e2e-gcp
ci/prow/e2e-aws-ovn-etcd-scaling d408adb link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-aws-disruptive d408adb link false /test e2e-aws-disruptive
ci/prow/e2e-vsphere-ovn-etcd-scaling d408adb link false /test e2e-vsphere-ovn-etcd-scaling

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.

@isabella-janssen
Copy link
Member

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 57e5a5c and 1 for PR HEAD d408adb in total

@openshift-merge-bot openshift-merge-bot bot merged commit f9cba4b into openshift:main May 23, 2025
38 of 55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@isabella-janssen isabella-janssen isabella-janssen left review comments

@deads2k deads2k Awaiting requested review from deads2k

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

Assignees

@neisw neisw

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@yuqi-zhang @djoshy @neisw @openshift-ci-robot @isabella-janssen