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.

Sign up for GitHub

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

Jump to bottom

Should validate connectivity from a pod to a non-node host address on same node flakes on v6 #4186

Open
tssurya opened this issue Feb 27, 2024 · 4 comments
Open

Should validate connectivity from a pod to a non-node host address on same node flakes on v6 #4186

tssurya opened this issue Feb 27, 2024 · 4 comments
Labels
ci-ipv6 Add support for IPV6 e2e's to run upstream

Comments

@tssurya
Copy link
Member

tssurya commented Feb 27, 2024 

2024-02-26T19:11:49.7464524Z �[0mtest e2e pod connectivity to host addresses �[0m�[1mShould validate connectivity from a pod to a non-node host address on same node�[0m
2024-02-26T19:11:49.7466459Z �[38;5;243m/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/e2e.go:960�[0m
2024-02-26T19:11:49.7467958Z   �[1mSTEP:�[0m Creating a kubernetes client �[38;5;243m@ 02/26/24 19:11:49.744�[0m
2024-02-26T19:11:49.7469141Z   Feb 26 19:11:49.744: INFO: >>> kubeConfig: /home/runner/ovn.conf
2024-02-26T19:11:49.7470766Z   �[1mSTEP:�[0m Building a namespace api object, basename node-e2e-to-host �[38;5;243m@ 02/26/24 19:11:49.745�[0m
2024-02-26T19:11:49.7557970Z   Feb 26 19:11:49.755: INFO: Skipping waiting for service account
2024-02-26T19:11:49.8388006Z   W0226 19:11:49.838024   62222 warnings.go:70] would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "e2e-src-ping-pod-container" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "e2e-src-ping-pod-container" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "e2e-src-ping-pod-container" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "e2e-src-ping-pod-container" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
2024-02-26T19:17:25.8606942Z   Feb 26 19:17:25.860: INFO: Warning: Failed to get logs from pod "e2e-src-ping-pod": the server rejected our request for an unknown reason (get pods e2e-src-ping-pod)
2024-02-26T19:17:25.8609794Z   Feb 26 19:17:25.860: INFO: Failed inside E2E framework:
2024-02-26T19:17:25.8612092Z       k8s.io/kubernetes/test/e2e/framework/pod.WaitForPodCondition({0x2b91fd0, 0xc00012e008}, {0x2bba080?, 0xc000c30000?}, {0xc000fc7fc8, 0x15}, {0x27656d0, 0x10}, {0xc000d19110, 0x13}, ...)
2024-02-26T19:17:25.8614877Z       	/home/runner/go/pkg/mod/k8s.io/kubernetes@v1.28.3/test/e2e/framework/pod/wait.go:227 +0x25f
2024-02-26T19:17:25.8647309Z       k8s.io/kubernetes/test/e2e/framework/pod.WaitForPodSuccessInNamespaceTimeout({0x2b91fd0, 0xc00012e008}, {0x2bba080, 0xc000c30000}, {0x27656d0, 0x10}, {0xc000fc7fc8, 0x15}, 0x0?)
2024-02-26T19:17:25.8670994Z       	/home/runner/go/pkg/mod/k8s.io/kubernetes@v1.28.3/test/e2e/framework/pod/wait.go:402 +0x177
2024-02-26T19:17:25.8672979Z       k8s.io/kubernetes/test/e2e/framework/pod.WaitForPodSuccessInNamespace(...)
2024-02-26T19:17:25.8674925Z       	/home/runner/go/pkg/mod/k8s.io/kubernetes@v1.28.3/test/e2e/framework/pod/wait.go:518
2024-02-26T19:17:25.8678698Z       github.com/ovn-org/ovn-kubernetes/test/e2e.checkConnectivityPingToHost(0xc000570c60, {0x2758f10, 0xa}, {0x27656d0, 0x10}, {0x279ad59, 0x26}, {0x274ddd6, 0x4}, 0x1e, ...)
2024-02-26T19:17:25.8681459Z       	/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/e2e.go:192 +0x5b8
2024-02-26T19:17:25.8683050Z       github.com/ovn-org/ovn-kubernetes/test/e2e.glob..func4.3()
2024-02-26T19:17:25.8684733Z       	/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/e2e.go:963 +0x5c
2024-02-26T19:17:25.8687203Z   �[38;5;9m[FAILED]�[0m in [It] - /home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/e2e.go:962 �[38;5;243m@ 02/26/24 19:17:25.86�[0m
2024-02-26T19:17:26.7012561Z   �[1mSTEP:�[0m dump namespace information after failure �[38;5;243m@ 02/26/24 19:17:26.7�[0m
2024-02-26T19:17:26.7014249Z   �[1mSTEP:�[0m Collecting events from namespace "node-e2e-to-host-4326". �[38;5;243m@ 02/26/24 19:17:26.7�[0m
2024-02-26T19:17:26.7034992Z   �[1mSTEP:�[0m Found 2 events. �[38;5;243m@ 02/26/24 19:17:26.703�[0m
2024-02-26T19:17:26.7039217Z   Feb 26 19:17:26.703: INFO: At 2024-02-26 19:11:50 +0000 UTC - event for e2e-src-ping-pod: {kubelet ovn

 Feb 26 19:17:26.703: INFO: At 2024-02-26 19:11:50 +0000 UTC - event for e2e-src-ping-pod: {kubelet ovn-worker} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b2dd04c3bcbfc571cfe785bcad902c8e415fcf824edb1624657a80597f0e1933": plugin type="ovn-k8s-cni-overlay" name="ovn-kubernetes" failed (add): failed to send CNI request: Post "http://dummy/": dial unix /var/run/ovn-kubernetes/cni//ovn-cni-server.sock: connect: connection refused
2024-02-26T19:17:26.7043378Z   Feb 26 19:17:26.703: INFO: At 2024-02-26 19:11:50 +0000 UTC - event for e2e-src-ping-pod: {kubelet ovn-worker} SandboxChanged: Pod sandbox changed, it will be killed and re-created.
2024-02-26T19:17:26.7057532Z   Feb 26 19:17:26.705: INFO: POD               NODE        PHASE    GRACE  CONDITIONS
2024-02-26T19:17:26.7062107Z   Feb 26 19:17:26.705: INFO: e2e-src-ping-pod  ovn-worker  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2024-02-26 19:11:49 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2024-02-26 19:11:49 +0000 UTC ContainersNotReady containers with unready status: [e2e-src-ping-pod-container]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2024-02-26 19:11:49 +0000 UTC ContainersNotReady containers with unready status: [e2e-src-ping-pod-container]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2024-02-26 19:11:49 +0000 UTC  }]
2024-02-26T19:17:26.7065512Z   Feb 26 19:17:26.705: INFO: 
2024-02-26T19:17:26.7088824Z   Feb 26 19:17:26.708: INFO: Unable to fetch node-e2e-to-host-4326/e2e-src-ping-pod/e2e-src-ping-pod-container logs: the server rejected our request for an unknown reason (get pods e2e-src-ping-pod)
2024-02-26T19:17:26.7114810Z   Feb 26 19:17:26.711: INFO: 
2024-02-26T19:17:26.7115644Z   Logging node info for node ovn-control-plane
2024-02-26T19:17:26.7194618Z   Feb 26 19:17:26.713: INFO: Node Info: &Node{ObjectMeta:{ovn-control-plane    cdae7697-62a4-4dfd-90dd-797d75813028 9826 0 2024-02-26 17:57:52 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/os:linux ingress-ready:true k8s.ovn.org/ovnkube-db:true k8s.ovn.org/zone-name:ovn-control-plane kubernetes.io/arch:amd64 kubernetes.io/hostname:ovn-control-plane kubernetes.io/os:linux node-role.kubernetes.io/control-plane:] map[k8s.ovn.org/host-cidrs:["fc00:f853:ccd:e793::3/64"] k8s.ovn.org/hybrid-overlay-distributed-router-gateway-ip:fd00:10:244:1::3 k8s.ovn.org/hybrid-overlay-distributed-router-gateway-mac:0a:58:cb:f0:b1:d3 k8s.ovn.org/l3-gateway-config:{"default":{"mode":"local","interface-id":"breth0_ovn-control-plane","mac-address":"02:42:ac:12:00:03","ip-addresses":["fc00:f853:ccd:e793::3/64"],"ip-address":"fc00:f853:ccd:e793::3/64","next-hops":["fc00:f853:ccd:e793::1"],"next-hop":"fc00:f853:ccd:e793::1","node-port-enable":"true","vlan-id":"0"}} k8s.ovn.org/network-ids:{"default":"0"} k8s.ovn.org/node-chassis-id:d0136e1c-6465-465d-b95b-834720b81ed5 k8s.ovn.org/node-gateway-router-lrp-ifaddr:{"ipv6":"fd98::2/64"} k8s.ovn.org/node-id:2 k8s.ovn.org/node-mgmt-port-mac-address:3e:bf:9f:49:b2:da k8s.ovn.org/node-primary-ifaddr:{"ipv6":"f
@tssurya
Copy link
Member Author

tssurya commented Feb 27, 2024

link to failure: #4106 (comment)

@tssurya tssurya added the ci-ipv6 Add support for IPV6 e2e's to run upstream label Feb 27, 2024
@github-actions GitHub Actions
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 May 29, 2024
@tssurya tssurya removed the lifecycle/stale All issues (> 60 days) and PRs (>90 days) with no activity. label May 29, 2024
@github-actions GitHub Actions
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 Jul 31, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 7, 2024

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 Aug 7, 2024
@tssurya tssurya reopened this Aug 22, 2024
@github-actions github-actions bot removed the lifecycle/stale All issues (> 60 days) and PRs (>90 days) with no activity. label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ci-ipv6 Add support for IPV6 e2e's to run upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tssurya