[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package systemd - 229-4ubuntu21.2 --- systemd (229-4ubuntu21.2) xenial; urgency=medium [ Dimitri John Ledkov ] * udev: Mark ndb devices as inactive until connected. (LP: #696435) * networkd: in dhcp, change UseMTU default to true, to accept DHCP provided MTU by default. (LP: #1717471) * sysctl: apply parameters in-order, instead of randomly. (LP: #1718444) * networkd: apply promote_secondaries, to make DHCP lease changes work. (LP: #1721223) * shutdown: sync filesystems, before going into a killing spree. (LP: #1722481) * sysctl: do not fail, when cannot apply sysctl changes due to read-only sysfs in containers. (LP: #1734409) * networkd,wait-online: add RequiredForOnline to mark mandatory/optional links for boot. (LP: #1737570) [ David Glasser ] * journald: don't reduce BurstRateLimit on low disk space (LP: #1732803) -- Dimitri John LedkovWed, 21 Feb 2018 13:46:37 + ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Configured lxd bridge network with 'raw.dnsmasq' option specifying MTU to be 1493. Started xenial container, and set it to use networkd, with DHCPv4, without specifying UseMTU= setting. With systemd 229-4ubuntu21.1, the container dhcp's and `ip a` output states that MTU is 1500. Upgrading to 229-4ubuntu21.2, and rebooting the container results in `ip a` output to state that MTU is 1492. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: In Progress Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package nplan - 0.32~17.04.1 --- nplan (0.32~17.04.1) zesty; urgency=medium * Backport 0.32 to 17.04. (LP: #1713142) nplan (0.32) bionic; urgency=medium * src/nm.c: better handle the UUID generation; the order of iterating through interaces may affect things here. Also make sure the tests catch a null UUID. nplan (0.31) bionic; urgency=medium [ Mathieu Trudel-Lapierre ] * src/nm.c: generate a UUID for a connection only as needed; when we're dealing with NM VLANs. (LP: #1712921) * debian/tests/autostart: Make the autostart test more verbose and avoid failing right from the start when systemd-networkd is disabled. (LP: #1699371) * tests/integration.py: bump the NetworkManager timeout for settling to 120 seconds, autopkgtest infrastructure tends to be a little slow for the network device configuration to be applied and noticed by NM. (LP: #1699371) [ Dimitri John Ledkov ] * Reload udevd to invalidate configuration cache of .rules/.link files as generate step may have changed them. LP: #1669564 [ Dan Streetman ] * Add another interface driver exception to netplan replug to prevent unbind of the Xen VIF interfaces. (LP: #1729573) nplan (0.30) artful; urgency=medium * Add an "optional" syntax node for now to all devices. This is unimplemented for now, but intended to allow users to mark some devices as optional: to make sure they do not delay boot when configured. (LP: #1664844) nplan (0.29) artful; urgency=medium * Fix autopkgtests in a world where /run/NetworkManager/conf.d already exists. nplan is enabled by default, so it might well have the directory already created on the filesystem. nplan (0.28) artful; urgency=medium * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It broke default network config in LXD and was contrary to the defaults used by the kernel. Reopens LP: 1655440. (LP: #1717404) * Add "accept-ra:" key for all device types; this will default to OFF but allow users to disable processing Router Advertisements when required by their network setup. (LP: #1655440) nplan (0.27) artful; urgency=medium [ Mathieu Trudel-Lapierre ] * Fix crash in systemd generator if called by an user on the command-line * coverage: fix exclusions to properly not cover our "never reached defaults" [ Dimitri John Ledkov ] * tests/integration.py: In teardown, stop systemd-networkd.socket. * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use. (LP: #1717471) * tests/integration.py: fix resolved detection. nplan (0.26) artful; urgency=medium * Bonding: - Add support for specifying a primary slave. (LP: #1709135) * Rebind: - Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting rebind. (LP: #1712224) * Autopkgtests: - Add allow-stderr. Systemd now bleats about a the networkd socket still being around and enabled when we restart the service; but we don't need to care since we're /restarting/ the service to load the new config. - Fix the autostart package to be more sensible: we don't really care if networkd autostarts or not, but we need to make sure that our generator will run at boot, so instead check the state, but only assert it once we've added a config file and before checking the state of our dummy device. - Do a bit more to make sure "mix" tests which stack virtual devices are as reliable as possible; by setting saner defaults. nplan (0.25) artful; urgency=medium * tests/generate.py: add a test to validate that correct blacklist entries are added when creating virtual devices. * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as the remaining interface and udev configuration can confuse NetworkManager now that it seems to manage random devices it did not create again. (LP: #1699371) * src/nm.c: set the MTU even though we also specify it in systemd-networkd for consumption by udev. NetworkManager will try to set it and might otherwise default to the wrong value. * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the same config, SLAAC), and don't have static addresses set. This should fix the cases where unconfigured devices still get an IPv6 address. (LP: #1655440) * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not configured; this follows the same logic as setting IPv6AcceptRA=no in networkd, with the exception that NM does not currently disable RAs. When it does, an unconfigured device for IPv6 will truly be left with no config. nplan (0.24) artful; urgency=medium * debian/control: set Priority to important to make sure we can get into minimal. -- Mathieu Trudel-LapierreThu, 16 Nov 2017 10:43:28 -0500 ** Changed in: nplan (Ubuntu Zesty) Status: Fix
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package nplan - 0.32~16.04.3 --- nplan (0.32~16.04.3) xenial; urgency=medium * tests/integration.py: Really fix skipping test_routes_v6 for the NM backend. nplan (0.32~16.04.2) xenial; urgency=medium * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied the skip rules for 16.04 after merging in 0.32. nplan (0.32~16.04.1) xenial; urgency=medium * Backport netplan 0.32 to 16.04. (LP: #1713142) * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave feature backported in that revision. * tests/integration.py: Skip tests that are still not yet supported in xenial nplan (0.32) bionic; urgency=medium * src/nm.c: better handle the UUID generation; the order of iterating through interaces may affect things here. Also make sure the tests catch a null UUID. nplan (0.31) bionic; urgency=medium [ Mathieu Trudel-Lapierre ] * src/nm.c: generate a UUID for a connection only as needed; when we're dealing with NM VLANs. (LP: #1712921) * debian/tests/autostart: Make the autostart test more verbose and avoid failing right from the start when systemd-networkd is disabled. (LP: #1699371) * tests/integration.py: bump the NetworkManager timeout for settling to 120 seconds, autopkgtest infrastructure tends to be a little slow for the network device configuration to be applied and noticed by NM. (LP: #1699371) [ Dimitri John Ledkov ] * Reload udevd to invalidate configuration cache of .rules/.link files as generate step may have changed them. LP: #1669564 [ Dan Streetman ] * Add another interface driver exception to netplan replug to prevent unbind of the Xen VIF interfaces. (LP: #1729573) nplan (0.30) artful; urgency=medium * Add an "optional" syntax node for now to all devices. This is unimplemented for now, but intended to allow users to mark some devices as optional: to make sure they do not delay boot when configured. (LP: #1664844) nplan (0.29) artful; urgency=medium * Fix autopkgtests in a world where /run/NetworkManager/conf.d already exists. nplan is enabled by default, so it might well have the directory already created on the filesystem. nplan (0.28) artful; urgency=medium * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It broke default network config in LXD and was contrary to the defaults used by the kernel. Reopens LP: 1655440. (LP: #1717404) * Add "accept-ra:" key for all device types; this will default to OFF but allow users to disable processing Router Advertisements when required by their network setup. (LP: #1655440) nplan (0.27) artful; urgency=medium [ Mathieu Trudel-Lapierre ] * Fix crash in systemd generator if called by an user on the command-line * coverage: fix exclusions to properly not cover our "never reached defaults" [ Dimitri John Ledkov ] * tests/integration.py: In teardown, stop systemd-networkd.socket. * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use. (LP: #1717471) * tests/integration.py: fix resolved detection. nplan (0.26) artful; urgency=medium * Bonding: - Add support for specifying a primary slave. (LP: #1709135) * Rebind: - Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting rebind. (LP: #1712224) * Autopkgtests: - Add allow-stderr. Systemd now bleats about a the networkd socket still being around and enabled when we restart the service; but we don't need to care since we're /restarting/ the service to load the new config. - Fix the autostart package to be more sensible: we don't really care if networkd autostarts or not, but we need to make sure that our generator will run at boot, so instead check the state, but only assert it once we've added a config file and before checking the state of our dummy device. - Do a bit more to make sure "mix" tests which stack virtual devices are as reliable as possible; by setting saner defaults. nplan (0.25) artful; urgency=medium * tests/generate.py: add a test to validate that correct blacklist entries are added when creating virtual devices. * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as the remaining interface and udev configuration can confuse NetworkManager now that it seems to manage random devices it did not create again. (LP: #1699371) * src/nm.c: set the MTU even though we also specify it in systemd-networkd for consumption by udev. NetworkManager will try to set it and might otherwise default to the wrong value. * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the same config, SLAAC), and don't have static addresses set. This should fix the cases where unconfigured devices still get an IPv6 address. (LP: #1655440) * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Verification-done for xenial 0.32~16.04.3, and zesty 0.32~17.04.1: UseMTU=yes is set on the interfaces for which a MTU is set, and the MTU coming from DHCP is applied correctly when running 'netplan apply'. ** Tags removed: verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial verification-done-zesty ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Autopktests still failing for xenial; the test is still not being skipped (we know it won't work on Xenial due to the version of NM shipped there). Marking verification-failed-xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the code skipping the test_routes_v6 test in the NetworkManager case. Therefore, it can't possibly pass SRU verification. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done-zesty ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Verification-done for zesty with nplan 0.29~17.04.1: I verified that the generated networkd config in the .network file contains "UseMTP=true" in the [DHCP] section; and the container gets the right MTU from the DHCP server. ** Tags removed: nplanfail verification-needed verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Verification-done for xenial with nplan 0.29~16.04.1: This was a regression in the development release that transpired in a new SRU that has not been migrated to the stable release. The bad version is 0.26; current state of nplan in xenial is 0.23~16.04.1 in -updates. Verified that lxc list shows an IPv4 and IPv6 address when a container is set up to use netplan with 0.29~16.04.1. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package systemd - 234-2ubuntu12 --- systemd (234-2ubuntu12) artful; urgency=medium [ Dimitri John Ledkov ] * debian/rules: do not strip test-copy. This insures test-copy is large enough for test-copy tests to pass. (LP: #1721203) [ Michael Biebl ] * Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf. All major NTP implementations ship a native service file nowadays with a Conflicts=systemd-timesyncd.service so this drop-in is no longer necessary. (Closes: #873185) (LP: #1721204) -- Dimitri John LedkovWed, 04 Oct 2017 13:28:34 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.29~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: New Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
** Description changed: + [Impact] + Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. + + [Test case] + 1) Run netplan on a system that should receive MTU settings from DHCP. + 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. + + [Regression Potential] + If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. + + --- + Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: New Status in systemd source package in Xenial: New Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in nplan source package in Xenial: New Status in systemd source package in Xenial: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
This bug was fixed in the package nplan - 0.27 --- nplan (0.27) artful; urgency=medium [ Mathieu Trudel-Lapierre ] * Fix crash in systemd generator if called by an user on the command-line * coverage: fix exclusions to properly not cover our "never reached defaults" [ Dimitri John Ledkov ] * tests/integration.py: In teardown, stop systemd-networkd.socket. * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use. (LP: #1717471) * tests/integration.py: fix resolved detection. -- Dimitri John LedkovFri, 15 Sep 2017 14:25:22 +0100 ** Changed in: nplan (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
** Changed in: nplan (Ubuntu) Status: New => Fix Committed ** Changed in: nplan (Ubuntu) Importance: Undecided => Critical ** Changed in: nplan (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Upstream pull request https://github.com/systemd/systemd/pull/6837 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
xnox> wgrant, t0mb0, veebers - i think i will just change ubuntu compiled in default for systemd-networkd to be honest. xnox: That sounds perilous. wgrant, had to google that word. wgrant, alternatives is to bake that into nplan, or bake that into the cloud-image alone xnox: nplan makes the most sense, IMO, rather than changing a confusing non-configurable upstream default silently in a distro patch. wgrant, i did that to accept search domains in resolved =/ because there is no easy way to set defaults for that, as it needs to go into the network file, and systemd only considers the first matching network file and ignores the rest (or some such) Er yeah, I meant .network in the ticket when I said .link. The .link is fine. systemd is so lovely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
netplan needs to set DHCP.UseMTU=yes If I do that, my local instance no longer behaves strangely, and the MTU is correctly 1458 ** Also affects: nplan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp