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
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
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
** 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
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
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
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:
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
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
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
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
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
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
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-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
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
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
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
** 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
** 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
** 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
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"
[
** 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
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
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
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
26 matches
Mail list logo
