Skip to content

OCPBUGS-57436: Add MCO test suite to 4.19 #29918

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
Open
wants to merge 3 commits into
base: release-4.19
Choose a base branch
from
Open

OCPBUGS-57436: Add MCO test suite to 4.19 #29918

wants to merge 3 commits into from

Conversation

yuqi-zhang
Copy link
Contributor

Manual cherrypick of #29776

@yuqi-zhang
Add new MCO disruptive suite
7a8e68c 
Add an empty MCO suite, for testing purposes. Future tests will be moved
over from serial and added via MCO OTE.
@yuqi-zhang
Add MCO disruptive suite
f15ae2c 
Many MCO tests require node disruption, so it was determined that these
would best live as a separate suite.

Create the MCO suite and move existing MCO tests in origin to it. The
next goal is to add On Cluster Layering tests to this as well,
potentially via OTE.
@yuqi-zhang
Run existing MCO tests in both serial and MCO suites
c1fe89b 
Eases transition
@yuqi-zhang
Copy link
Contributor Author

/jira cherrypick OCPBUGS-57435

@openshift-ci-robot
Copy link

@yuqi-zhang: Jira Issue OCPBUGS-57435 has been cloned as Jira Issue OCPBUGS-57436. Will retitle bug to link to clone.
/retitle OCPBUGS-57436: Add MCO test suite to 4.19

In response to this:

/jira cherrypick OCPBUGS-57435

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 openshift-ci bot changed the title Add MCO test suite to 4.19 OCPBUGS-57436: Add MCO test suite to 4.19 Jun 13, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 13, 2025
@openshift-ci-robot
Copy link

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-57436, which is invalid:

  • expected dependent Jira Issue OCPBUGS-57435 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead
  • expected dependent Jira Issue OCPBUGS-57435 to target a version in 4.20.0, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Manual cherrypick of #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 openshift-ci bot requested review from cheesesashimi and deads2k June 13, 2025 00:58
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuqi-zhang
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

@yuqi-zhang
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 13, 2025
@openshift-ci-robot
Copy link

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-57436, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-57435 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-57435 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

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 openshift-ci bot requested a review from sergiordlr June 13, 2025 01:03
@yuqi-zhang
Copy link
Contributor Author

/retest-required

@yuqi-zhang yuqi-zhang mentioned this pull request Jun 13, 2025
Open
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 13, 2025

@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-gcp-ovn-rt-upgrade c1fe89b link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout c1fe89b link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/okd-scos-e2e-aws-ovn c1fe89b link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade c1fe89b link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn c1fe89b link false /test e2e-openstack-ovn

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.

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

@cheesesashimi cheesesashimi Awaiting requested review from cheesesashimi

@deads2k deads2k Awaiting requested review from deads2k

@sergiordlr sergiordlr Awaiting requested review from sergiordlr

Assignees
No one assigned
Labels
jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@yuqi-zhang @openshift-ci-robot