Bug 1475460
| Summary: | Path MTU discovery not working when run from OpenStack | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan Lebon <jlebon> |
| Component: | docker | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | adimania, admiller, amurdaca, dcbw, dwalsh, emrakova, eparis, fkluknav, ichavero, jcajka, lsm5, marianne, miabbott, mpatel, nalin, riek, sean, vbatts, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-29 11:59:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jonathan Lebon
2017-07-26 18:03:08 UTC
This looks useful: https://blog.cloudflare.com/path-mtu-discovery-in-practice/ It looks like in this: https://github.com/projectcalico/calicoctl/issues/488 They discussed ensuring the MTU isn't *larger* than the host routes, which makes sense to me. Also found: https://github.com/openshift/openshift-ansible/pull/544/commits/c28aea2f19b6aea729f27b636e5318ac775addb6 which looks to me like it hardcodes a default of 1450? This could possibly go back as far as docker 1.10. We've been hitting this for a long time. See the following, which I believe are all related. https://bugzilla.redhat.com/show_bug.cgi?id=1333961 https://bugzilla.redhat.com/show_bug.cgi?id=1357116 https://projects.engineering.redhat.com/browse/CENTRALCI-1749 http://post-office.corp.redhat.com/archives/ci-infra-list/2017-March/msg00036.html *** Bug 1474793 has been marked as a duplicate of this bug. *** I see this constantly on Fedora 26 with docker or with firejail. In both cases I see the issue when I have a network namespace (from docker or firejail) connected to a bridged network interface and have an openconnect VPN session open. In these cases all MTUs are 1500, except vpn0 (from openconnect) with an MTU of 1274. Traffic from outside a namespace is fine, going through the vpn or not. Traffic from inside the name space that doesn't go oever the VPN is fine. But when it goes over the VPN, tcpdump shows large response packets are getting sent by remote servers, then dropped by vpn0. I was able to work around this by manually setting the MTU inside the namespace to 1274 to match the VPN. Any updates on this? This is a constant source of frustration and gotchas. Eric, Mrunal and Dan, any ideas on this? Is this something we could fix with CRI-O? Something fixable in CNI? One thing I wonder is if we should try delegating at least some of the bridge device creation to NetworkManager, which is in somewhat of a better position to understand the host routing state. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |