Skip to content

MCO-1580: MCO-1581: Achieving parity with MCO node disruption frequency #4996

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 1 commit into
base: main
Choose a base branch
from
Open

MCO-1580: MCO-1581: Achieving parity with MCO node disruption frequency #4996

wants to merge 1 commit into from

Conversation

dkhater-redhat
Copy link
Contributor

- What I did

- How to verify it

- Description for the changelog

@dkhater-redhat dkhater-redhat marked this pull request as draft April 22, 2025 15:37
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 22, 2025
@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 Apr 22, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkhater-redhat

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 Apr 22, 2025
@dkhater-redhat dkhater-redhat changed the title Change mcdiffb DRAFT MCO-1580: MCO-1581: Achieving parity with MCO node disruption frequency Apr 23, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 23, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 23, 2025 •
edited by openshift-ci bot
Loading

@dkhater-redhat: This pull request references MCO-1580 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.19.0" version, but no target version was set.

In response to this:

- What I did

- How to verify it

- Description for the changelog

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.

@dkhater-redhat dkhater-redhat force-pushed the change-mcdiffb branch 7 times, most recently from 8452b7a to 32555ad Compare April 28, 2025 17:22
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 28, 2025
@dkhater-redhat dkhater-redhat force-pushed the change-mcdiffb branch 3 times, most recently from ef4dc03 to 621dc6c Compare April 28, 2025 23:16
@dkhater-redhat dkhater-redhat marked this pull request as ready for review April 28, 2025 23:51
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 28, 2025
@dkhater-redhat dkhater-redhat changed the title DRAFT MCO-1580: MCO-1581: Achieving parity with MCO node disruption frequency MCO-1580: MCO-1581: Achieving parity with MCO node disruption frequency Apr 28, 2025
@dkhater-redhat dkhater-redhat force-pushed the change-mcdiffb branch 2 times, most recently from 633afa0 to db06f06 Compare April 29, 2025 15:16
@dkhater-redhat dkhater-redhat force-pushed the change-mcdiffb branch 3 times, most recently from 5281786 to 3347699 Compare April 29, 2025 15:29
@cheesesashimi @dkhater-redhat
unify update paths for non-OCL and OCL and avoid reboots by recreatin…
0c73a25 
…g and reusing MOSB's with updated rendered spec
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 29, 2025

@dkhater-redhat: 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-azure-ovn-upgrade-out-of-change 0c73a25 link false /test e2e-azure-ovn-upgrade-out-of-change
ci/prow/okd-scos-e2e-aws-ovn 0c73a25 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-op-ocl 0c73a25 link false /test e2e-gcp-op-ocl

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

@djoshy djoshy Awaiting requested review from djoshy

@isabella-janssen isabella-janssen Awaiting requested review from isabella-janssen

@LorbusChris LorbusChris Awaiting requested review from LorbusChris

@RishabhSaini RishabhSaini Awaiting requested review from RishabhSaini

Assignees
No one assigned
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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@dkhater-redhat @openshift-ci-robot @openshift-merge-robot @cheesesashimi