This bug was fixed in the package systemd - 229-4ubuntu21
---
systemd (229-4ubuntu21) xenial; urgency=medium
* networkd: do not uncoditionally apply NOARP.
* networkd: fix size of MTUBytes so that it does not overwrites ARP.
* Fixes regression-updates LP: #1727301
-- Dimitri
the updates-proposed build works in my case as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
To manage
** Tags removed: regression-updates
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
$ dpkg -l | grep 229-4
ii libpam-systemd:amd64229-4ubuntu21
amd64system and service
manager - PAM module
ii libsystemd-dev:amd64229-4ubuntu21
Hello Markus, 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
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
- * Setting [Link] MTUBytes= in .network file has a side-effect of
+ * Setting [Link] MTUBytes= in .network file has a side-effect of
overflowing and setting NOARP flag. This is not intended behaviour /
regression.
- * Trying to fix above by setting
** Description changed:
[Impact]
- * Incomplete cherrypick of ARP functionality in networkd resulted in an
- undesired side-effect, specifically NOARP flag started to be applied
- unconditionally, specifically when it should not have, resulting in loss
- of network connectivity.
+ *
** Changed in: systemd (Ubuntu Zesty)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
The ppa package works for my use case. Maybe add this test-case to QA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu Zesty)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Artful)
Status: Fix
aha, i need to specify anything that requires to call the code path to
adjust any flags from non default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option
I have packages built with above patch applied, which I suspect is the missing
portion to fix this.
It is available from this ppa
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3015
$ sudo add-apt-repository ppa:ci-train-ppa-service/3015
$ sudo apt-get update
I am failing to
** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
To
** Description changed:
+ [Impact]
+
+ * Incomplete cherrypick of ARP functionality in networkd resulted in an
+ undesired side-effect, specifically NOARP flag started to be applied
+ unconditionally, specifically when it should not have, resulting in loss
+ of network connectivity.
+
+ * This
I am suspecting the following cherrypick is missing in xenial:
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
will prepare a PPA with this fix applied, and will expedite an sru with
this fix in.
** Bug watch added: github.com/systemd/systemd/issues
I could solve this issue by rebuilding the debian packages without two
patches:
- networkd-add-support-to-configure-NOARP-ARP-for-interface.patch
- networkd-bond-support-primary-slave-and-active-slave-4873.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We have the same problem without bond configured. After upgrading to
systemd 229-4ubuntu20 NOARP is set to our network interfaces. The
machine has two network interfaces and the configuration is very simple:
# 50-ens5f0.network
[Match]
MACAddress=24:8a:7:11:50:a8
[Link]
MTUBytes=9000
[Network]
We are also affected by this suddenly after systemd upgrade the network
was gone, had to go in via serial console.
We are only using networkd because Martin Pitt said in the run-up to the
16.04 release that networkd would be supported and to be used in the
next LTS release.
# networkctl
IDX
the networking is configured via systemd-networkd.
bonding module is loaded with 'max_bonds=0' to address upcoming systemd change
https://github.com/systemd/systemd/issues/6184
pre-upgrade:
# networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
How are eth0/eth1/bond0 configured?
Do you use netplan and networkd?
Do you use ifupdown?
Can you paste the output of $ networkctl?
Copies of the configuration e.g.:
/etc/network/interfaces
/etc/network/interfaces.d/*
/etc/netplan/*
/run/systemd/network/*
/etc/systemd/network/*
--
You
21 matches
Mail list logo
