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 gateway failover tests fails in 0.18 #3031

Closed
aswinsuryan opened this issue May 31, 2024 · 1 comment · Fixed by #3069
Closed

Wireguard gateway failover tests fails in 0.18 #3031

aswinsuryan opened this issue May 31, 2024 · 1 comment · Fixed by #3069
Assignees
Labels
bug Something isn't working priority:medium wireguard
Projects

Comments

@aswinsuryan
Copy link
Contributor

What happened:Wireguard gateway failover tests fails in 0.18

What you expected to happen: The tests should pass

How to reproduce it (as minimally and precisely as possible): Run e2e in 0.18 branch, the logs are attached.

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:
    [
    submariner-gather.zip
    ](url)
@yboaron
Copy link
Contributor

yboaron commented Jul 4, 2024

The root cause for this issue is wireguard submariner network interface created with new ifindex after GW pod restarted, meaning all host routes created in route agent pod with LinkIndex pointing to previous wireguard submariner ifindex are deleted.

To workaround this issue we can restart the route-agent pod on gateway node.

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: Done
Backlog
Backlog
Development

Successfully merging a pull request may close this issue.

3 participants