Skip to content

[release-4.19] NO-JIRA: Update CNO reviewers/approvers #2765

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.

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

Open
wants to merge 1 commit into
base: release-4.19
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2756

/assign jcaamano

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

Copy link
Contributor

openshift-ci bot commented Aug 6, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: 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-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-serial-ipsec, 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-dualstack-bgp-local-gw-techpreview, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview, 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/hypershift-e2e-aks

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

Copy link
Contributor

openshift-ci bot commented Aug 7, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: 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/e2e-aws-hypershift-ovn-kubevirt, ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-aws-ovn-single-node, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-upgrade, ci/prow/e2e-network-mtu-migration-ovn-ipv4, ci/prow/e2e-vsphere-ovn-dualstack-primaryv6, ci/prow/okd-scos-e2e-aws-ovn, ci/prow/security

In response to this:

/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/e2e-aws-hypershift-ovn-kubevirt
/override ci/prow/e2e-aws-ovn-hypershift-conformance
/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-network-mtu-migration-ovn-ipv4
/override ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/security

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.

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 c8c1f37 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-hypershift-ovn-kubevirt c8c1f37 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/security c8c1f37 link false /test security
ci/prow/okd-scos-e2e-aws-ovn c8c1f37 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-hypershift-conformance c8c1f37 link true /test e2e-aws-ovn-hypershift-conformance
ci/prow/e2e-aws-ovn-single-node c8c1f37 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-serial c8c1f37 link false /test e2e-aws-ovn-serial

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

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
@asood-rh
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 11, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request explicitly references no jira issue.

In response to this:

This is an automated cherry-pick of #2756

/assign jcaamano

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 11, 2025
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. 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. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.