Skip to content

[release-4.19] OCPBUGS-60117: Enable test for LGW L2#30052

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30009-to-release-4.19
Aug 18, 2025
Merged

[release-4.19] OCPBUGS-60117: Enable test for LGW L2#30052
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30009-to-release-4.19

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #30009

/assign arkadeepsen

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 4, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CORENET-6203

Details

In response to this:

This is an automated cherry-pick of #30009

/assign arkadeepsen

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 review from danwinship and knobunc August 4, 2025 18:24
@arkadeepsen
Copy link
Copy Markdown
Member

/test ?

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Aug 4, 2025

@arkadeepsen: 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 okd-scos-images
/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

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
pull-ci-openshift-origin-release-4.19-e2e-aws-csi
pull-ci-openshift-origin-release-4.19-e2e-aws-disruptive
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn
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-etcd-scaling
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-aws-proxy
pull-ci-openshift-origin-release-4.19-e2e-azure
pull-ci-openshift-origin-release-4.19-e2e-azure-ovn-etcd-scaling
pull-ci-openshift-origin-release-4.19-e2e-azure-ovn-upgrade
pull-ci-openshift-origin-release-4.19-e2e-gcp-csi
pull-ci-openshift-origin-release-4.19-e2e-gcp-disruptive
pull-ci-openshift-origin-release-4.19-e2e-gcp-fips-serial
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn-etcd-scaling
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
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-dualstack-local-gateway
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-metal-ipi-serial
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-serial-ovn-ipv6
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-virtualmedia
pull-ci-openshift-origin-release-4.19-e2e-openstack-ovn
pull-ci-openshift-origin-release-4.19-e2e-openstack-serial
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn-dualstack-primaryv6
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn-etcd-scaling
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-okd-scos-images
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
Details

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.

@arkadeepsen
Copy link
Copy Markdown
Member

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

@arkadeepsen
Copy link
Copy Markdown
Member

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Aug 4, 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-aws-disruptive b3c606d link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 b3c606d link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-openstack-serial b3c606d link false /test e2e-openstack-serial
ci/prow/e2e-aws-ovn-single-node-upgrade b3c606d link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-etcd-scaling b3c606d link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-openstack-ovn b3c606d link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-etcd-scaling b3c606d link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive b3c606d link false /test e2e-gcp-disruptive
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 b3c606d link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-vsphere-ovn-etcd-scaling b3c606d link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-azure-ovn-upgrade b3c606d link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-etcd-scaling b3c606d link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial b3c606d link false /test e2e-gcp-fips-serial
ci/prow/e2e-metal-ipi-ovn-dualstack b3c606d link false /test e2e-metal-ipi-ovn-dualstack

Full PR test history. Your PR dashboard.

Details

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.

@arkadeepsen
Copy link
Copy Markdown
Member

/retitle [release-4.19] OCPBUGS-60117: Enable test for LGW L2

@openshift-ci openshift-ci bot changed the title [release-4.19] CORENET-6203: Enable test for LGW L2 [release-4.19] OCPBUGS-60117: Enable test for LGW L2 Aug 5, 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 Aug 5, 2025
@openshift-ci-robot
Copy link
Copy Markdown

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

  • expected Jira Issue OCPBUGS-60117 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.

Details

In response to this:

This is an automated cherry-pick of #30009

/assign arkadeepsen

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.

@arkadeepsen
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 5, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@arkadeepsen: This pull request references Jira Issue OCPBUGS-60117, 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 text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-60116 is in the state Closed (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-60116 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

Details

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 5, 2025
@openshift-ci openshift-ci bot requested a review from anuragthehatter August 5, 2025 02:26
@arkadeepsen
Copy link
Copy Markdown
Member

/hold
until openshift/ovn-kubernetes#2688 is merged

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 5, 2025
@arkadeepsen
Copy link
Copy Markdown
Member

openshift/ovn-kubernetes#2688 is merged

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

@arkadeepsen
Copy link
Copy Markdown
Member

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 11, 2025
@arkadeepsen
Copy link
Copy Markdown
Member

/cc @jcaamano

@openshift-ci openshift-ci bot requested a review from jcaamano August 11, 2025 11:35
@jcaamano
Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 11, 2025
@anuragthehatter
Copy link
Copy Markdown

/label cherry-pick-approved
/label qe-approved

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Aug 11, 2025

@anuragthehatter: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

Details

In response to this:

/label cherry-pick-approved
/label qe-approved

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 bot added the qe-approved Signifies that QE has signed off on this PR label Aug 11, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-60117, which is valid.

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 POST, 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-60116 is in the state Closed (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-60116 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

Details

In response to this:

This is an automated cherry-pick of #30009

/assign arkadeepsen

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
Copy Markdown
Contributor

/approve

1 similar comment
@knobunc
Copy link
Copy Markdown
Contributor

knobunc commented Aug 18, 2025

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Aug 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Aug 18, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit f05f4aa into openshift:release-4.19 Aug 18, 2025
40 of 54 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60117: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #30009

/assign arkadeepsen

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
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

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

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-08-19-141357

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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants