Skip to content

Conversation

@jcaamano
Copy link
Contributor

@jcaamano jcaamano commented Apr 2, 2025

ricky-rav and others added 24 commits March 20, 2025 18:07
Add flows at prio=102 to allow traffic from the OVN network to the host network to be handled normally by the bridge instead of forwarding it directly to the NIC (which would be done by the flow at prio=100). This allows pods in the default network to reach localnet pods (whose network is mapped to breth0) on the same node and vice versa.

Add two extra flows for icmpv6 to allow neighbor solicitation and neighbor advertisement messages to pass.

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Add e2e tests where a server pod is connected to a secondary localnet and pods in the default network try to reach the server pod on its localnet interface. The localnet is plugged to breth0 and IPs on the localnet interface are drawn from the subnets of the node primary interface addresses.
Two cases to check:
- client and server pods are on different nodes (works with existing code)
- client and server pods are on the same node (works thanks to the previous commit with extra openflow rule at prio=102)

Verify the reachability of the server through curl for TCP and ping for ICMP echo request/reply.

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Allow default network pods to reach localnet on the same node
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
The current localnet kubevirt live migration tests are implemented using
persistent IPs, this change add similar version of those tests but for
ipamless localnet where VMI and pod IPs are statically assigned.

Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Clean up duplciated network ID on internal routeimport controller
structure which is already available in NetInfo

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>
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>
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>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Some tests where interleaving ACCEPT and DROP iptables rules while
others where just checking if the DROP rule was there. The check would
pass if the DROP was in place but not necessaily hit if it had an ACCEPT
rule over it.

Change all tests to latter mechanism.

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
go get k8s.io/api@v0.32.3
go get k8s.io/client-go@v0.32.3
go get k8s.io/component-helpers@v0.32.3
go get k8s.io/kubernetes@v1.32.3
go get k8s.io/apiextensions-apiserver@v1.32.3
go get k8s.io/apiextensions-apiserver@v0.32.3
go get sigs.k8s.io/controller-runtime@v0.20.3
go mod tidy
go mod vendor

GO version was bumped to v1.23, aligned linter version. Had to move
away from giantswarm since it was no longer providing useful v1.23
images and it's unknown to me why we would not be using a more official
image anyway.

Had to bump metallb to v0.14.8 as it would no longer build otherwise.

kind was updated to v0.27 and kindest/node to v1.32.3 as well. kindest/node
v1.32+ is only compatible with kind v0.27+ but metallb relies on their
own incompatible build of kind so had to patch it to use our kind
installation.

Fixed lint issues.

Updated contrib/kind.sh, CI e2e manifests and codegen.

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
go get k8s.io/kubernetes@v1.32.2
go get k8s.io/api@v0.32.2
go get k8s.io/client-go@v0.32.2
go get k8s.io/pod-security-admission@v0.32.2
go get k8s.io/kubectl@v0.32.2
go get sigs.k8s.io/controller-runtime@v0.20.3
go get k8s.io/mount-utils@v0.32.2
go get k8s.io/cri-client@v0.32.2
go get k8s.io/dynamic-resource-allocation@v0.32.2
go get k8s.io/kube-scheduler@v0.32.2
go get k8s.io/csi-translation-lib@v0.32.2
go get k8s.io/cloud-provider@v0.32.2
go get k8s.io/controller-manager@v0.32.2
go get sigs.k8s.io/apiserver-network-proxy/konnectivity-client@v0.32.0
go mod tidy

Updated kind, kubectl and k8s test binaries.

controller-manager no longer registers the kubeconfig flag so we can go
back to using the test framework utility methods for it rather than
working around it.

Added skips for new Alpha/Beta features introduced in v1.32

Fixed a kubevirt test issue which could not activate DHCP on a UDN veth
because the device was unmanaged after upgrade to kindest/node v1.32+

Worked around two metallb issues
metallb/metallb#2723
metallb/metallb#2724

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>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 2, 2025

/test ?

@jcaamano jcaamano changed the title Dmerge 20250402 Downstream Merge 2025-04-02 Apr 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 2, 2025

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

/test 4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
/test 4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade
/test 4.19-upgrade-from-stable-4.18-images
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-local-gateway
/test e2e-aws-ovn-local-to-shared-gateway-mode-migration
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-shared-to-local-gateway-mode-migration
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-local-gateway
/test e2e-aws-ovn-windows
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn
/test e2e-gcp-ovn-techpreview
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test gofmt
/test images
/test lint
/test qe-perfscale-payload-control-plane-6nodes
/test unit

The following commands are available to trigger optional jobs:

/test e2e-agent-compact-ipv4
/test e2e-aws-ovn-clusternetwork-cidr-expansion
/test e2e-aws-ovn-fdp-qe
/test e2e-aws-ovn-hypershift-conformance-techpreview
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-techpreview
/test e2e-aws-ovn-virt-techpreview
/test e2e-azure-ovn
/test e2e-azure-ovn-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview
/test e2e-metal-ipi-ovn-dualstack-techpreview
/test e2e-metal-ipi-ovn-ipv4
/test e2e-metal-ipi-ovn-ipv6-techpreview
/test e2e-metal-ipi-ovn-techpreview
/test e2e-openstack-ovn
/test e2e-ovn-hybrid-step-registry
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-techpreview
/test e2e-vsphere-windows
/test okd-scos-e2e-aws-ovn
/test okd-scos-images
/test openshift-e2e-gcp-ovn-techpreview-upgrade
/test ovncore-perfscale-aws-ovn-large-cluster-density-v2
/test ovncore-perfscale-aws-ovn-large-node-density-cni
/test ovncore-perfscale-aws-ovn-xlarge-cluster-density-v2
/test ovncore-perfscale-aws-ovn-xlarge-node-density-cni
/test perfscale-aws-ovn-medium-cluster-density-v2
/test perfscale-aws-ovn-medium-node-density-cni
/test perfscale-aws-ovn-small-cluster-density-v2
/test perfscale-aws-ovn-small-node-density-cni
/test qe-perfscale-aws-ovn-small-udn-density-l2
/test qe-perfscale-aws-ovn-small-udn-density-l3
/test security

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

pull-ci-openshift-ovn-kubernetes-master-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-master-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-ovn-kubernetes-master-4.19-upgrade-from-stable-4.18-images
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-hypershift
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-hypershift-conformance-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-local-gateway
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-local-to-shared-gateway-mode-migration
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-serial
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-shared-to-local-gateway-mode-migration
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-single-node-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-upgrade-local-gateway
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-windows
pull-ci-openshift-ovn-kubernetes-master-e2e-azure-ovn
pull-ci-openshift-ovn-kubernetes-master-e2e-azure-ovn-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-azure-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn
pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack-bgp-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-dualstack-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-ipv6-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-metal-ipi-ovn-techpreview
pull-ci-openshift-ovn-kubernetes-master-e2e-openstack-ovn
pull-ci-openshift-ovn-kubernetes-master-e2e-ovn-hybrid-step-registry
pull-ci-openshift-ovn-kubernetes-master-e2e-vsphere-ovn
pull-ci-openshift-ovn-kubernetes-master-e2e-vsphere-ovn-techpreview
pull-ci-openshift-ovn-kubernetes-master-gofmt
pull-ci-openshift-ovn-kubernetes-master-images
pull-ci-openshift-ovn-kubernetes-master-lint
pull-ci-openshift-ovn-kubernetes-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-ovn-kubernetes-master-openshift-e2e-gcp-ovn-techpreview-upgrade
pull-ci-openshift-ovn-kubernetes-master-security
pull-ci-openshift-ovn-kubernetes-master-unit
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.

@openshift-ci openshift-ci bot requested review from trozet and tssurya April 2, 2025 13:45
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2025
@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 2, 2025

needs
#2380
#2379

@ricky-rav
Copy link
Contributor

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

@ricky-rav: This pull request references Jira Issue OCPBUGS-43004, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ysegev@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-54199, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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 Apr 2, 2025
@jluhrsen
Copy link
Contributor

jluhrsen commented Apr 2, 2025

/retitle CORENET-5666,OCPBUGS-43004,OCPBUGS-54199: Downstream Merge 2025-04-02

@openshift-ci openshift-ci bot changed the title OCPBUGS-43004,OCPBUGS-54199: Downstream Merge 2025-04-02 CORENET-5666,OCPBUGS-43004,OCPBUGS-54199: Downstream Merge 2025-04-02 Apr 2, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 2, 2025

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

This pull request references Jira Issue OCPBUGS-43004, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ysegev@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-54199, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

cc @ricky-rav

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 Apr 3, 2025

/retest-required

@pliurh
Copy link
Contributor

pliurh commented Apr 3, 2025

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

@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 3, 2025

/test qe-perfscale-aws-ovn-small-udn-density-l2
/test qe-perfscale-aws-ovn-small-udn-density-l3

@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 4, 2025

/retest

@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 4, 2025

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

@jcaamano
Copy link
Contributor Author

jcaamano commented Apr 4, 2025

/override ci/prow/e2e-aws-ovn-windows

https://issues.redhat.com/browse/OCPBUGS-54499

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-aws-ovn-windows

Details

In response to this:

/override ci/prow/e2e-aws-ovn-windows

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 Author

jcaamano commented Apr 4, 2025

/retest

@jluhrsen
Copy link
Contributor

jluhrsen commented Apr 4, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, jluhrsen

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

openshift-ci bot commented Apr 5, 2025

@jcaamano: 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-metal-ipi-ovn-dualstack-techpreview 1d6dfc8 link false /test e2e-metal-ipi-ovn-dualstack-techpreview
ci/prow/e2e-vsphere-ovn-techpreview 1d6dfc8 link false /test e2e-vsphere-ovn-techpreview
ci/prow/security 1d6dfc8 link false /test security
ci/prow/e2e-metal-ipi-ovn-ipv6-techpreview 1d6dfc8 link false /test e2e-metal-ipi-ovn-ipv6-techpreview
ci/prow/e2e-metal-ipi-ovn-techpreview 1d6dfc8 link false /test e2e-metal-ipi-ovn-techpreview
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview 1d6dfc8 link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-aws-ovn-hypershift-conformance-techpreview 1d6dfc8 link false /test e2e-aws-ovn-hypershift-conformance-techpreview
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview 1d6dfc8 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 253890a into openshift:master Apr 5, 2025
34 of 42 checks passed
@openshift-ci-robot
Copy link
Contributor

@jcaamano: Jira Issue OCPBUGS-43004: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Jira Issue OCPBUGS-54199: All pull requests linked via external trackers have merged:

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

Details

In response to this:

cc @ricky-rav

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: ovn-kubernetes-base
This PR has been included in build ose-ovn-kubernetes-base-container-v4.20.0-202504062308.p0.g253890a.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-microshift
This PR has been included in build ovn-kubernetes-microshift-container-v4.20.0-202504062308.p0.g253890a.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-ovn-kubernetes
This PR has been included in build ose-ovn-kubernetes-container-v4.20.0-202504062308.p0.g253890a.assembly.stream.el9.
All builds following this will include this PR.

@ricky-rav
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@ricky-rav: Jira Issue OCPBUGS-43004: All pull requests linked via external trackers have merged:

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

Jira Issue OCPBUGS-54199 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

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.

@jluhrsen
Copy link
Contributor

/revert

jluhrsen added a commit to jluhrsen/ovn-kubernetes-1 that referenced this pull request May 24, 2025
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
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.

8 participants