Skip to content

[release-4.18] NO-JIRA: Update CNO reviewers/approvers #2766

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: release-4.18
Choose a base branch
from
Open

[release-4.18] NO-JIRA: Update CNO reviewers/approvers #2766

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #2756

/assign jcaamano

@jcaamano
Update CNO reviwers/approvers
f10907d 
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]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 6, 2025
Merged
@jcaamano
Copy link
Contributor

jcaamano commented Aug 6, 2025

/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade-ipsec
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-azure-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-images
/override ci/prow/e2e-aws-hypershift-ovn-kubevirt
/override ci/prow/e2e-aws-ovn-hypershift-conformance
/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial-ipsec
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-aws-ovn-upgrade
/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-aws-ovn-windows
/override ci/prow/e2e-azure-ovn
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-network-mtu-migration-ovn-ipv4
/override ci/prow/e2e-network-mtu-migration-ovn-ipv6
/override ci/prow/e2e-openstack-ovn
/override ci/prow/e2e-ovn-hybrid-step-registry
/override ci/prow/e2e-ovn-ipsec-step-registry
/override ci/prow/e2e-ovn-step-registry
/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-vsphere-ovn-dualstack
/override ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/override ci/prow/hypershift-e2e-aks

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 6, 2025

@jcaamano: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
  • ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade-ipsec
  • ci/prow/4.19-upgrade-from-stable-4.18-e2e-azure-ovn-upgrade
  • ci/prow/4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-upgrade
  • ci/prow/4.19-upgrade-from-stable-4.18-images
  • ci/prow/e2e-aws-ovn-serial-ipsec
  • ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
  • ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview
  • ci/prow/hypershift-e2e-aks

Only the following failed contexts/checkruns were expected:

  • ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
  • ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade-ipsec
  • ci/prow/4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
  • ci/prow/4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-upgrade
  • ci/prow/4.18-upgrade-from-stable-4.17-images
  • ci/prow/e2e-aws-hypershift-ovn-kubevirt
  • ci/prow/e2e-aws-ovn-hypershift-conformance
  • ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • ci/prow/e2e-aws-ovn-serial
  • ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • ci/prow/e2e-aws-ovn-single-node
  • ci/prow/e2e-aws-ovn-upgrade
  • ci/prow/e2e-aws-ovn-upgrade-ipsec
  • ci/prow/e2e-aws-ovn-windows
  • ci/prow/e2e-azure-ovn
  • ci/prow/e2e-azure-ovn-upgrade
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-gcp-ovn-upgrade
  • ci/prow/e2e-metal-ipi-ovn-ipv6
  • ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
  • ci/prow/e2e-network-mtu-migration-ovn-ipv4
  • ci/prow/e2e-network-mtu-migration-ovn-ipv6
  • ci/prow/e2e-openstack-ovn
  • ci/prow/e2e-ovn-hybrid-step-registry
  • ci/prow/e2e-ovn-ipsec-step-registry
  • ci/prow/e2e-ovn-step-registry
  • ci/prow/e2e-vsphere-ovn
  • ci/prow/e2e-vsphere-ovn-dualstack
  • ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
  • ci/prow/images
  • ci/prow/lint
  • ci/prow/okd-scos-e2e-aws-ovn
  • ci/prow/okd-scos-images
  • ci/prow/security
  • ci/prow/unit
  • ci/prow/verify
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-hypershift-ovn-kubevirt
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-hypershift-conformance
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-serial
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-upgrade-ipsec
  • pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-windows
  • pull-ci-openshift-cluster-network-operator-master-e2e-azure-ovn
  • pull-ci-openshift-cluster-network-operator-master-e2e-azure-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn
  • pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-cluster-network-operator-master-e2e-metal-ipi-ovn-ipv6-ipsec
  • pull-ci-openshift-cluster-network-operator-master-e2e-network-mtu-migration-ovn-ipv4
  • pull-ci-openshift-cluster-network-operator-master-e2e-network-mtu-migration-ovn-ipv6
  • pull-ci-openshift-cluster-network-operator-master-e2e-openstack-ovn
  • pull-ci-openshift-cluster-network-operator-master-e2e-ovn-hybrid-step-registry
  • pull-ci-openshift-cluster-network-operator-master-e2e-ovn-ipsec-step-registry
  • pull-ci-openshift-cluster-network-operator-master-e2e-ovn-step-registry
  • pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn
  • pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack
  • pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack-primaryv6
  • pull-ci-openshift-cluster-network-operator-master-images
  • pull-ci-openshift-cluster-network-operator-master-lint
  • pull-ci-openshift-cluster-network-operator-master-okd-scos-e2e-aws-ovn
  • pull-ci-openshift-cluster-network-operator-master-okd-scos-images
  • pull-ci-openshift-cluster-network-operator-master-security
  • pull-ci-openshift-cluster-network-operator-master-unit
  • pull-ci-openshift-cluster-network-operator-master-verify
  • pull-ci-openshift-cluster-network-operator-release-4.18-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-release-4.18-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade-ipsec
  • pull-ci-openshift-cluster-network-operator-release-4.18-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-release-4.18-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-cluster-network-operator-release-4.18-4.18-upgrade-from-stable-4.17-images
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade-ipsec
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-azure-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-upgrade
/override ci/prow/4.19-upgrade-from-stable-4.18-images
/override ci/prow/e2e-aws-hypershift-ovn-kubevirt
/override ci/prow/e2e-aws-ovn-hypershift-conformance
/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial-ipsec
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-aws-ovn-upgrade
/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-aws-ovn-windows
/override ci/prow/e2e-azure-ovn
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-network-mtu-migration-ovn-ipv4
/override ci/prow/e2e-network-mtu-migration-ovn-ipv6
/override ci/prow/e2e-openstack-ovn
/override ci/prow/e2e-ovn-hybrid-step-registry
/override ci/prow/e2e-ovn-ipsec-step-registry
/override ci/prow/e2e-ovn-step-registry
/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-vsphere-ovn-dualstack
/override ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/override ci/prow/hypershift-e2e-aks

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.

@jcaamano
Copy link
Contributor

jcaamano commented Aug 7, 2025

/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-upgrade

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 7, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-azure-ovn-upgrade, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-upgrade

In response to this:

/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-upgrade

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-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 7, 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/e2e-vsphere-ovn-dualstack-primaryv6 f10907d link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-hypershift-ovn-kubevirt f10907d link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/security f10907d link false /test security
ci/prow/e2e-azure-ovn-upgrade f10907d link true /test e2e-azure-ovn-upgrade
ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade f10907d link false /test 4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn f10907d link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-serial f10907d link false /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-single-node f10907d link false /test e2e-aws-ovn-single-node
ci/prow/e2e-vsphere-ovn-dualstack f10907d link false /test e2e-vsphere-ovn-dualstack

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.

@kyrtapz
Copy link
Contributor

kyrtapz commented Aug 7, 2025

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 7, 2025
@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 7, 2025
@kyrtapz
Copy link
Contributor

kyrtapz commented Aug 11, 2025

/lgtm

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, openshift-cherrypick-robot

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

@asood-rh
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JacobTanenbaum JacobTanenbaum Awaiting requested review from JacobTanenbaum

@tssurya tssurya Awaiting requested review from tssurya

Assignees

@mffiedler mffiedler

@eurijon eurijon

@jcaamano jcaamano

@anuragthehatter anuragthehatter

@huiran0826 huiran0826

@asood-rh asood-rh

@jechen0648 jechen0648

@imatza-rh imatza-rh

@qiowang721 qiowang721

@Meina-rh Meina-rh

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.