Skip to content

OCPBUGS-59391: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests #29989

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

Merged
merged 6 commits into from
Jul 17, 2025

Conversation

arghosh93
Copy link

This PR cherry picks BGP E2E tests into release-4.19 branch.

No merge conflicts

jcaamano and others added 6 commits July 15, 2025 22:56
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Don't turn off EgressIP advertisement for the default network in the
default RouteAdvertisements to avoid racing between tests.

Signed-off-by: Peng Liu <pliu@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
stderr may contain logs unrelated with the ran command that may disrupt
parsing. Observed as [1] in [2].

1.
  I0523 06:49:35.567480 83973 client.go:952] Running 'oc --namespace=e2e-test-bgp-zlvr5 --kubeconfig=/tmp/secret/kubeconfig exec ovnkube-node-l2rv4 -n openshift-ovn-kubernetes -c ovnkube-controller -- /bin/bash -c ovs-vsctl get Port enp2s0 Interfaces'
  I0523 06:49:36.203600 83973 client.go:952] Running 'oc --namespace=e2e-test-bgp-zlvr5 --kubeconfig=/tmp/secret/kubeconfig exec ovnkube-node-l2rv4 -n openshift-ovn-kubernetes -c ovnkube-controller -- /bin/bash -c ovs-vsctl get Interface E0523 06:49:36.044467   85723 websocket.go:296] Unknown stream id 1 Type'

2.
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1925763835906494464

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
@openshift-ci openshift-ci bot requested review from celebdor and danwinship July 15, 2025 17:33
@arghosh93 arghosh93 changed the title [release-4.19] : Sync ovn-kubernetes bgp e2e tests NO-JIRA: OVNK BGP: [release-4.19] : Sync ovn-kubernetes bgp e2e tests Jul 15, 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 Jul 15, 2025
@openshift-ci-robot
Copy link

@arghosh93: This pull request explicitly references no jira issue.

In response to this:

This PR cherry picks BGP E2E tests into release-4.19 branch.

No merge conflicts

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.

@arghosh93
Copy link
Author

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview

@arghosh93
Copy link
Author

/retest

@jcaamano
Copy link
Contributor

/test ?

Copy link
Contributor

openshift-ci bot commented Jul 16, 2025

@jcaamano: The following commands are available to trigger required jobs:

/test e2e-aws-jenkins
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-ovn
/test e2e-gcp-ovn-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test images
/test lint
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-ovn-virt-techpreview
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-csi
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial
/test e2e-metal-ipi-serial-ovn-ipv6
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-metal-ovn-two-node-arbiter
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-origin-release-4.19-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-release-4.19-e2e-aws-csi
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-fips
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-serial-1of2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-serial-2of2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-release-4.19-e2e-gcp-csi
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-release-4.19-e2e-hypershift-conformance
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-dualstack-bgp-techpreview
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.19-e2e-openstack-ovn
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-release-4.19-images
pull-ci-openshift-origin-release-4.19-lint
pull-ci-openshift-origin-release-4.19-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-release-4.19-unit
pull-ci-openshift-origin-release-4.19-verify
pull-ci-openshift-origin-release-4.19-verify-deps

In response to this:

/test ?

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

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview

@arghosh93
Copy link
Author

@jcaamano tests in these two lanes passed in last run.

@jcaamano
Copy link
Contributor

@jcaamano tests in these two lanes passed in last run.

Yeah, I might have missed that. I see that you triggered e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview manually but why would e2e-metal-ipi-ovn-dualstack-bgp-techpreview run?

@jcaamano
Copy link
Contributor

jcaamano commented Jul 16, 2025

retitle CORENET-6148: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests

@jcaamano
Copy link
Contributor

jcaamano commented Jul 16, 2025

/retitle CORENET-6148: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests

@openshift-ci openshift-ci bot changed the title NO-JIRA: OVNK BGP: [release-4.19] : Sync ovn-kubernetes bgp e2e tests CORENET-6148: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests Jul 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@arghosh93: This pull request references CORENET-6148 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.z" version, but no target version was set.

In response to this:

This PR cherry picks BGP E2E tests into release-4.19 branch.

No merge conflicts

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.

@jcaamano
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@jcaamano: This pull request references CORENET-6148 which is a valid jira issue.

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.

@jcaamano
Copy link
Contributor

/lgtm
/approve

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

/retitle OCPBUGS-59391: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests

@openshift-ci openshift-ci bot changed the title CORENET-6148: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests OCPBUGS-59391: [release-4.19]: OVNK BGP: Sync ovn-kubernetes bgp e2e tests Jul 16, 2025
@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 16, 2025
@openshift-ci-robot
Copy link

@arghosh93: This pull request references Jira Issue OCPBUGS-59391, which is invalid:

  • expected the bug to target only the "4.19.z" version, but multiple target versions were set
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-59391 to depend on a bug targeting a version in 4.20.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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 PR cherry picks BGP E2E tests into release-4.19 branch.

No merge conflicts

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.

@arghosh93
Copy link
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 16, 2025
@openshift-ci-robot
Copy link

@arghosh93: This pull request references Jira Issue OCPBUGS-59391, 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.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-59392 is in the state Release Pending (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-59392 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

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.

@neisw
Copy link
Contributor

neisw commented Jul 16, 2025

/approve

Copy link
Contributor

openshift-ci bot commented Jul 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arghosh93, jcaamano, neisw

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 Jul 16, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a2dcd48 and 2 for PR HEAD 75efff3 in total

Copy link
Contributor

openshift-ci bot commented Jul 17, 2025

@arghosh93: The following test 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-single-node-serial 75efff3 link false /test e2e-aws-ovn-single-node-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.

@openshift-merge-bot openshift-merge-bot bot merged commit 4efb164 into openshift:release-4.19 Jul 17, 2025
33 of 34 checks passed
@openshift-ci-robot
Copy link

@arghosh93: Jira Issue OCPBUGS-59391: All pull requests linked via external trackers have merged:

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

In response to this:

This PR cherry picks BGP E2E tests into release-4.19 branch.

No merge conflicts

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202507170208.p0.g4efb164.assembly.stream.el9.
All builds following this will include this PR.

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