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

Automated cherry pick of #5409: Enable IPv6 on OVS internal port if needed in bridging mode #5437

Conversation

antoninbas
Copy link
Contributor

Cherry pick of #5409 on release-1.13.

#5409: Enable IPv6 on OVS internal port if needed in bridging mode

For details on the cherry pick process, see the cherry pick requests page.

@antoninbas antoninbas added the kind/cherry-pick Categorizes issue or PR as related to the cherry-pick of a bug fix from the main branch to a release label Aug 24, 2023
@antoninbas
Copy link
Contributor Author

/test-all
/test-flexible-ipam-e2e

The uplink interface may have an IPv6 address, while the interface
created by OVS for the internal port may not support IPv6. For example,
such a situation has been observed in a Kind cluster, with IPv6 enabled
on the uplink but disbled by default on new interfaces:

```
root@kind-worker:/# sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1
root@kind-worker:/# sysctl net.ipv6.conf.default.disable_ipv6
net.ipv6.conf.default.disable_ipv6 = 1
root@kind-worker:/# sysctl net.ipv6.conf.eth0.disable_ipv6
net.ipv6.conf.eth0.disable_ipv6 = 0
```

When we detect that uplink addresses include an IPv6 address, we will
now ensure that IPv6 is enabled on the bridge port (using sysctl),
before attempting to move the addresses over. If it fails, we will
proceed with the rest of the initialization, but moving the IP addresses
to the bridge is very likely to be unsuccessful in that case.

We also make bridge cleanup more robust, by saving all uplink IP
addresses in the uplink config, and using the saved values to restore
the uplink interface. This ensures that cleanup can succeed, even if
bridge configuration failed half-way, as was the case in antrea-io#5368.

Fixes antrea-io#5368

Signed-off-by: Antonin Bas <abas@vmware.com>
@antoninbas antoninbas force-pushed the automated-cherry-pick-of-#5409-upstream-release-1.13 branch from 07ddabd to d6c3197 Compare August 24, 2023 19:06
@antoninbas
Copy link
Contributor Author

/test-all
/test-flexible-ipam-e2e

@luolanzone
Copy link
Contributor

@antoninbas
The flexible ipam e2e job is not stable, I think Ran is still working on this to triage it. @gran-vmv any finding so far for the test failure?

@gran-vmv
Copy link
Contributor

@antoninbas The flexible ipam e2e job is not stable, I think Ran is still working on this to triage it. @gran-vmv any finding so far for the test failure?

The FlexibleIPAM e2e issue is tracked in #5451 , but we still need more discussion to fix this data plane bug.

@tnqn tnqn merged commit 7577a50 into antrea-io:release-1.13 Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cherry-pick Categorizes issue or PR as related to the cherry-pick of a bug fix from the main branch to a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants