Skip to content
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

UDN, non-IC: egress on layer2 topology e2e tests fail on non-IC deployments #4642

Open
maiqueb opened this issue Aug 20, 2024 · 2 comments
Open
Labels
kind/bug All issues that are bugs and PRs opened to fix bugs

Comments

@maiqueb
Copy link
Contributor

maiqueb commented Aug 20, 2024

What happened?

The e2e tests about egress on layer2 topology are failing on non-IC deployments:

• [FAILED] [256.356 seconds]
Network Segmentation pod2Egress on a user defined primary network can be accessed to from the pods running in the Kubernetes cluster [It] by one pod with dualstack addresses over a layer2 network
/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/network_segmentation.go:762

  [FAILED] Timed out after 120.000s.
  Expected success, but got an error:
      <exec.CodeExitError>: 
      error running /usr/local/bin/kubectl --server=https://127.0.0.1:41447/ --kubeconfig=/home/runner/ovn.conf --namespace=network-segmentation-2127 exec client-pod -- curl --connect-timeout 2 172.18.0.5:9000:
      Command stdout:
      
      stderr:
        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                       Dload  Upload   Total   Spent    Left  Speed
      
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
      curl: (28) Connection timeout after 2000 ms
      command terminated with exit code 28
      
      error:
      exit status 28
      {
          Err: <*errors.errorString | 0xc0011e0030>{
              s: "error running /usr/local/bin/kubectl --server=https://127.0.0.1:41447/ --kubeconfig=/home/runner/ovn.conf --namespace=network-segmentation-2127 exec client-pod -- curl --connect-timeout 2 172.18.0.5:9000:\nCommand stdout:\n\nstderr:\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0\ncurl: (28) Connection timeout after 2000 ms\ncommand terminated with exit code 28\n\nerror:\nexit status 28",
          },
          Code: 28,
      }
  In [It] at: /home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/network_segmentation.go:755 @ 08/20/24 08:54:57.028

We currently do not have a way to support this for non-IC.

It will probably involve a new design.

What did you expect to happen?

The e2e tests should pass.

How can we reproduce it (as minimally and precisely as possible)?

Run the UDN layer2 topology egress e2e tests on a non-IC cluster.

Check the presubmit results on the network segmentation, non-IC deployment lane after #4561 is merged.

Anything else we need to know?

No response

OVN-Kubernetes version

All

Kubernetes version

All

OVN version

$ oc rsh -n ovn-kubernetes ovnkube-node-xxxxx (pick any ovnkube-node pod on your cluster)
$ rpm -q ovn
# paste output here

OVS version

$ oc rsh -n ovn-kubernetes ovs-node-xxxxx (pick any ovs pod on your cluster)
$ rpm -q openvswitch
# paste output here

Platform

Is it baremetal? GCP? AWS? Azure?

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

@maiqueb maiqueb added the kind/bug All issues that are bugs and PRs opened to fix bugs label Aug 20, 2024
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the lifecycle/stale All issues (> 60 days) and PRs (>90 days) with no activity. label Oct 22, 2024
Copy link

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
@maiqueb maiqueb reopened this Oct 27, 2024
@github-actions github-actions bot removed the lifecycle/stale All issues (> 60 days) and PRs (>90 days) with no activity. label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug All issues that are bugs and PRs opened to fix bugs
Projects
None yet
Development

No branches or pull requests

1 participant