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

Support running IPV6 and EgressIP #4130

Closed
tssurya opened this issue Feb 6, 2024 · 4 comments · Fixed by #4580
Closed

Support running IPV6 and EgressIP #4130

tssurya opened this issue Feb 6, 2024 · 4 comments · Fixed by #4580
Assignees
Labels
ci-ipv6 Add support for IPV6 e2e's to run upstream

Comments

@tssurya
Copy link
Member

tssurya commented Feb 6, 2024

As part of #4106 we have added 3 new lanes:

  1. Control Plane, shared, IPV6, IC
  2. Control Plane, local, IPV6, IC
  3. Control Plane, shared, IPV6, nonIC

EgressIP e2e's are failing because the infrastructure is not stable. I had to skip them. See #4106 (comment) Healthchecks were failing over v6 nodeIPs thus causing EIPs to never get assigned to nodes because the nodes were deemed to be not reachable and down.

Sample failures;
https://github.com/ovn-org/ovn-kubernetes/actions/runs/7796371932/job/21261668937?pr=4106
https://github.com/ovn-org/ovn-kubernetes/actions/runs/7796371932/job/21261669451?pr=4106
https://github.com/ovn-org/ovn-kubernetes/actions/runs/7796371932/job/21261668236?pr=4106

Goal: Troubleshoot why this happens and fix it and re-enable the tests

@tssurya tssurya added the ci-ipv6 Add support for IPV6 e2e's to run upstream label Feb 6, 2024
@tssurya
Copy link
Member Author

tssurya commented Feb 6, 2024

W0206 08:52:32.241467      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:33.242511      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:33.242511      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:35.239203      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:35.239203      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:36.239748      16 egressip_healthcheck.go:162] Could not connect to ovn-control-plane ([fd00:10:244:1::2]:9107): context deadline exceeded
W0206 08:52:36.239748      16 egressip_healthcheck.go:162] Could not connect to ovn-control-plane ([fd00:10:244:1::2]:9107): context deadline exceeded
W0206 08:52:36.239815      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:36.239815      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:37.240351      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:37.240351      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:37.240461      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:37.240461      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:38.241467      16 egressip_healthcheck.go:162] Could not connect to ovn-worker ([fd00:10:244:2::2]:9107): context deadline exceeded
W0206 08:52:38.241467      16 egressip_healthcheck.go:162] Could not connect to ovn-worker ([fd00:10:244:2::2]:9107): context deadline exceeded
W0206 08:52:40.238660      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:40.238660      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:41.239521      16 egressip_healthcheck.go:162] Could not connect to ovn-control-plane ([fd00:10:244:1::2]:9107): context deadline exceeded
W0206 08:52:41.239521      16 egressip_healthcheck.go:162] Could not connect to ovn-control-plane ([fd00:10:244:1::2]:9107): context deadline exceeded
W0206 08:52:41.239563      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:41.239563      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:42.240249      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:42.240249      16 egressip_healthcheck.go:162] Could not connect to ovn-worker2 ([fd00:10:244:3::2]:9107): context deadline exceeded
W0206 08:52:42.240294      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:42.240294      16 egressip_healthcheck.go:145] Health checking using insecure connection
W0206 08:52:43.240976      16 egressip_healthcheck.go:162] Could not connect to ovn-worker ([fd00:10:244:2::2]:9107): context deadline exceeded
W0206 08:52:43.240976      16 egressip_healthcheck.go:162] Could not connect to ovn-worker ([fd00:10:244:2::2]:9107): context deadline exceeded

sample output from cluster-manager

@martinkennelly martinkennelly self-assigned this Feb 29, 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 May 30, 2024
@tssurya tssurya removed the lifecycle/stale All issues (> 60 days) and PRs (>90 days) with no activity. label Jun 3, 2024
Copy link

github-actions bot commented Aug 3, 2024

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 Aug 3, 2024
Copy link

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

Successfully merging a pull request may close this issue.

3 participants