Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2799

/assign pliurh

fedepaol and others added 3 commits September 22, 2025 13:25
This allows to keep the list in a single place while reusing them also
in sub directories, where we might want to expand that list.

Signed-off-by: Federico Paolinelli <[email protected]>
(cherry picked from commit 6497b7d)
Removing trozet as he left the company. Adding tssurya as team lead
replacement.

Adding pliurh as approver replacing dougbtv who will be eventually
removed after some soak period as he moved on to other unrelated
projects. pliurh has demonstrated extensive experience working on this
repository througout his work on sdn->ovnk different migration modes.

Added bpickard22 to help as a reviewer for multus related changes as a
replacement for dougbtv.

Adding the overall core network team as responsible to perform reviews.

Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
(cherry picked from commit 1704438)
CI bot verification blocks change to OWNERS_ALIASES as fepan is
not a member of the org.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-61765 has been cloned as Jira Issue OCPBUGS-62055. Will retitle bug to link to clone.
/retitle [release-4.16] [Release 4.17] OCPBUGS-62055: Update CNO reviewers/approvers

In response to this:

This is an automated cherry-pick of #2799

/assign pliurh

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 [release-4.16] [Release 4.17] OCPBUGS-61765: Update CNO reviewers/approvers [release-4.16] [Release 4.17] OCPBUGS-62055: Update CNO reviewers/approvers Sep 22, 2025
@openshift-ci-robot openshift-ci-robot added 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 Sep 22, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-62055, which is invalid:

  • expected dependent Jira Issue OCPBUGS-61765 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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:

This is an automated cherry-pick of #2799

/assign pliurh

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.

Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign abhat 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

Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

@openshift-cherrypick-robot: 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/security 0c7ea27 link false /test security
ci/prow/e2e-azure-ovn 0c7ea27 link false /test e2e-azure-ovn
ci/prow/4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade 0c7ea27 link false /test 4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade
ci/prow/4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade-ipsec 0c7ea27 link false /test 4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade-ipsec
ci/prow/4.16-upgrade-from-stable-4.15-e2e-azure-ovn-upgrade 0c7ea27 link false /test 4.16-upgrade-from-stable-4.15-e2e-azure-ovn-upgrade
ci/prow/e2e-aws-live-migration-sdn-ovn-rollback 0c7ea27 link false /test e2e-aws-live-migration-sdn-ovn-rollback

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.

@pliurh
Copy link
Contributor

pliurh commented Sep 25, 2025

/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 Sep 25, 2025
@openshift-ci-robot
Copy link
Contributor

@pliurh: This pull request references Jira Issue OCPBUGS-62055, 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.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-61765 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-61765 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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.

@pliurh
Copy link
Contributor

pliurh commented Sep 25, 2025

/retest-required

@pliurh
Copy link
Contributor

pliurh commented Sep 25, 2025

/cherry-pick release-4.15

@openshift-cherrypick-robot
Copy link
Author

@pliurh: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.15

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.

@pliurh
Copy link
Contributor

pliurh commented Sep 26, 2025

/retitle [release-4.16] OCPBUGS-62055: Update CNO reviewers/approvers

@openshift-ci openshift-ci bot changed the title [release-4.16] [Release 4.17] OCPBUGS-62055: Update CNO reviewers/approvers [release-4.16] OCPBUGS-62055: Update CNO reviewers/approvers Sep 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Development

Successfully merging this pull request may close these issues.

5 participants