Skip to content

Conversation

@ingvagabund
Copy link
Member

@ingvagabund ingvagabund commented Jul 15, 2025

through node affinities focusing on ready and reacheable control plane nodes first.

Rebasing and extending #1990.

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

@ingvagabund: This pull request references Jira Issue OCPBUGS-50992, which is invalid:

  • expected the bug to target the "4.20.0" version, 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:

through node affinities focusing on ready and reacheable control plane nodes first.

Rebasing and extending https://github.com/openshift/oc/pull/1990/files.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 15, 2025
@openshift-ci openshift-ci bot requested review from ardaguclu and deads2k July 15, 2025 15:13
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2025
@ingvagabund ingvagabund force-pushed the 1990-rebase branch 2 times, most recently from 0c27e1f to 0069453 Compare July 15, 2025 15:16
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2025
@ricardomaraschini
Copy link
Contributor

/retest

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 19, 2025
@ingvagabund
Copy link
Member 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 Jul 19, 2025
@openshift-ci-robot
Copy link

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhouying7780

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 zhouying7780 July 19, 2025 09:54
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 19, 2025

@ingvagabund: 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-aws-ovn-serial 0069453 link true /test e2e-aws-ovn-serial
ci/prow/e2e-metal-ipi-ovn-ipv6 b50b11f link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/security b50b11f link false /test security

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.

@ingvagabund
Copy link
Member Author

/retest-required

@ricardomaraschini
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Jul 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, ricardomaraschini

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-merge-bot openshift-merge-bot bot merged commit 1baef05 into openshift:main Jul 21, 2025
15 of 17 checks passed
@openshift-ci-robot
Copy link

@ingvagabund: Jira Issue OCPBUGS-50992: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-50992 has been moved to the MODIFIED state.

In response to this:

through node affinities focusing on ready and reacheable control plane nodes first.

Rebasing and extending #1990.

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.

@ingvagabund ingvagabund deleted the 1990-rebase branch July 21, 2025 08:26
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-tools
This PR has been included in build ose-tools-container-v4.20.0-202507211916.p0.g1baef05.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-cli
This PR has been included in build openshift-enterprise-cli-container-v4.20.0-202507211916.p0.g1baef05.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-deployer
This PR has been included in build openshift-enterprise-deployer-container-v4.20.0-202507211916.p0.g1baef05.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cli-artifacts
This PR has been included in build ose-cli-artifacts-container-v4.20.0-202507211916.p0.g1baef05.assembly.stream.el9.
All builds following this will include this PR.

midu16 added a commit to midu16/oc that referenced this pull request Sep 17, 2025
midu16 added a commit to midu16/oc that referenced this pull request Sep 17, 2025
midu16 added a commit to midu16/oc that referenced this pull request Sep 17, 2025
@midu16
Copy link
Contributor

midu16 commented Nov 3, 2025

/cherry-pick release-4.19

@openshift-cherrypick-robot

@midu16: new pull request created: #2124

In response to this:

/cherry-pick release-4.19

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.

@midu16
Copy link
Contributor

midu16 commented Nov 3, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot

@midu16: new pull request created: #2127

In response to this:

/cherry-pick release-4.18

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.

@midu16
Copy link
Contributor

midu16 commented Nov 3, 2025

/cherry-pick release-4.17

@midu16
Copy link
Contributor

midu16 commented Nov 3, 2025

/cherry-pick release-4.16

@openshift-cherrypick-robot

@midu16: new pull request created: #2128

In response to this:

/cherry-pick release-4.17

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.

@openshift-cherrypick-robot

@midu16: new pull request created: #2129

In response to this:

/cherry-pick release-4.16

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.

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-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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants