[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Released Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Released Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2~cloud0 --- openvswitch (2.8.1-0ubuntu0.17.10.2~cloud0) xenial-pike; urgency=medium . * New update for the Ubuntu Cloud Archive. . openvswitch (2.8.1-0ubuntu0.17.10.2) artful; urgency=medium . * d/p/dpif-kernel-gre-mtu-workaround.patch, d/p/dpif-netlink-rtnl-Use-65000-instead-of-65535-as-tunnel-MTU.patch: Cherry pick in-flight fixes for workaround to correctly set MTU of GRE devices via netlink (LP: #1742505). ** Changed in: cloud-archive/pike Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Released Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
successfully tested with bug 1743746 ** Tags removed: verification-needed-artful verification-queens-needed ** Tags added: verification-done-artful verification-queens-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
This bug was fixed in the package openvswitch - 2.8.1-0ubuntu3 --- openvswitch (2.8.1-0ubuntu3) bionic; urgency=medium * Updates to systemd configuration: - Move to distinct units for ovsdb-server and ovs-vswitchd. * Drop obsolete upstart configuration file. * Bump nofiles to 1048576 for ovs daemons (LP: #1737866). * d/control: Bump minimum debhelper version to 10, drop BD on dh-systemd. * d/p/dpif-kernel-gre-mtu-workaround.patch, d/p/dpif-netlink-rtnl-Use-65000-instead-of-65535-as-tunnel-MTU.patch: Cherry pick in-flight fixes for workaround to correctly set MTU of GRE devices via netlink (LP: #1742505). -- James PageThu, 18 Jan 2018 15:26:41 +0200 ** Changed in: openvswitch (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Tested OK on Xenial with Pike UCA: 16: gre_sys@NONE:mtu 65000 qdisc pfifo_fast master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 56:5c:6e:19:f5:4b brd ff:ff:ff:ff:ff:ff However testing on artful currently blocked pending resolution of bug 1743746 which prevents an increase in the MTU of the gre devices. ** Tags removed: verification-pike-needed ** Tags added: verification-pike-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
@james-page When will the 2.8.1 release be? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
I've uploaded the fixes for this issue to bionic (currently in proposed awaiting builds across all archs) and for artful (stacked ontop of the current 2.8.1 stable release in proposed). I'd like todo this fix ontop of the 2.8.1 release, rather than have end- users deal with two sets of updates which are disruptive to the data plane in an openstack cloud. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Leaving the kernel bug tasks open for now; there is an underlying issue in the kernel specific to GRE tunnel ports where the MTU passed during new device creation is not being used; the fixes to OVS workaround this issue rather than actually resolving it. ** Description changed: + [Impact] + OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. + + [Test Case] + Deploy OpenStack Pike (xenial + pike UCA or artful) + Create tenant networks using GRE segmentation + Boot instances + Instance networking will be broken/slow + + gre_sys devices will be set to mtu=1472 on hypervisor hosts. + + [Regression Potential] + Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). + + + [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
I've re-tested with the proposed changes upstream; MTU is correctly set to 65000 for all tunnel types including GRE on 4.4 kernels; the kernel fix for bug 1743746 is required for support on >= Artful or if the HWE edge kernel is in use on Xenial. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Test packages for Artful and Xenial in: ppa:james-page/pike -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Reference bug 1743746 for MTU hardware limitation in 4.13 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Simple reproducer: sudo add-apt-repository cloud-archive:pike sudo apt update sudo apt install openvswitch-switch sudo ovs-vsctl add-br br-tun sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre options:remote_ip=10.100.1.1 this will cause ovs to create the gre_sys device in the kernel; the remote_ip can be anything but is obviously not functional. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
ovs-dev ML thread: https://mail.openvswitch.org/pipermail/ovs-dev/2018-January/343069.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Mirroring some of the thread on the ovs dev ML: >From Christina "Thanks Eric, that matches my findings, glad that there seems to be an accepted fix already. But it is fairly recent and only in since 4.15-rc8 levels afaik. But OTOH its description at [1] reads pretty much like my notes so far. @James - do you think you could test a super-recent mainline kernel build from [2] in regard to this issue? [1]: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8/; This kernel fix resolves a secondary issue I saw with the 4.13 kernel where the workaround we used for 4.4 did not work - the kernel was applying a 1500 max limit to all GRE devices. This was fixed in [1] which I've confirmed on my test but the original OVS bug still exists - gre_sys is still configured with MTU 1472, implying the IFLA_MTU value provided via netlink is being ignored by the kernel. ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
Marking kernel tasks as confirmed as we have at least one related bug which we have confirmed is fixed under 4.15 (and looks like an easy pick for 4.13). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Incomplete Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Incomplete Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp