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

Wireguard cable drive fails in clusters with OVNKubernetes CNI #3032

Open
aswinsuryan opened this issue May 31, 2024 · 3 comments
Open

Wireguard cable drive fails in clusters with OVNKubernetes CNI #3032

aswinsuryan opened this issue May 31, 2024 · 3 comments
Assignees
Labels
bug Something isn't working priority:medium wireguard

Comments

@aswinsuryan
Copy link
Contributor

What happened:Wireguard cable drive fails in clusters with OVNKubernetes CNI . The gateways are not connected.

What you expected to happen: The gateways should be connected and the. end to end test should pass.

How to reproduce it (as minimally and precisely as possible): Deploy submarienr in a with OVNKubernetes clusters with wireguard as cable driver

Anything else we need to know?:

Environment:

  • Diagnose information (use subctl diagnose all):
  • Gather information (use subctl gather):
  • Cloud provider or hardware configuration:
  • Install tools:
  • Others:
@aswinsuryan aswinsuryan added the bug Something isn't working label May 31, 2024
@dfarrell07
Copy link
Member

This user does seem to be using Wireguard, Yossi pointed out: #2934

Tom did some looking and suspected the Wireguard CI failover/restart issue might be related to KIND version bump, not a code change on our side. Aswin says maybe some IP routes or other resources are going missing during restarts.

Maybe should add a KI that 0.18 doesn't work perfectly with Wireguard+OVNKubernetes: https://submariner.io/operations/known-issues/

Aswin did some testing with OpenShiftSDN and also saw this issue.

@dfarrell07
Copy link
Member

Related: #3031

Copy link
Contributor

github-actions bot commented Oct 9, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 9, 2024
@dfarrell07 dfarrell07 removed the stale label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:medium wireguard
Projects
Status: Backlog
Development

No branches or pull requests

3 participants