Bug 1460235
Summary: | [3.5] Docker MTU is wrong when SDN is adjusted to smaller MTU | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
Component: | Installer | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.0 | CC: | aos-bugs, jialiu, jokerman, mmccomas, obedin, wmeng |
Target Milestone: | --- | ||
Target Release: | 3.5.z | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Starting with OCP 3.4, OpenShift's SDN plugins no longer reconfigure the docker bridge MTU, rather pods are configured properly on creation. Because of this change, non-OpenShift containers may have an MTU configured that is too large to allow access to hosts on the SDN. The installer has been updated to align the MTU setting for the docker bridge with the MTU used inside the cluster, thus avoiding the problem.
|
Story Points: | --- |
Clone Of: | 1457062 | Environment: | |
Last Closed: | 2017-06-29 13:33:14 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: | |||
Bug Depends On: | 1457062 | ||
Bug Blocks: | 1460233 |
Comment 1
Scott Dodson
2017-06-26 14:42:43 UTC
erified this bug with openshift-ansible-3.5.88-1.git.0.9901d92.el7.noarch, and PASS. [root@openshift-151 ~]# cat /etc/sysconfig/docker-network # /etc/sysconfig/docker-network DOCKER_NETWORK_OPTIONS=' --mtu=1350' [root@openshift-151 ~]# grep -i mtu /etc/origin/node/node-config.yaml mtu: 1350 [root@openshift-151 ~]# oc new-app https://github.com/oybed/test-network -n install-test [root@openshift-151 ~]# oc get build -n install-test NAME TYPE FROM STATUS STARTED DURATION test-network-1 Docker Git@71c648f Complete 22 minutes ago 3m33s Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1666 |