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 affe
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
Verification-done zesty with 0.32~17.04.01:
Tested bond in balance-tlb mode and active-backup mode, both correctly
set the primary for the bond.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ub
Verification-done xenial with 0.32~16.04.3:
Testing bonding in active-backup and balance-tlb mode; in both cases
when primary: is set, that device it correctly set to be used as the
primary slave, as shown in both /proc/net/bonding/bond0 and
/sys/class/net/bond0/bonding/primary.
** Tags removed:
Verification-done-artful with 0.32~17.10.1:
Bonding in active-backup mode with primary: set to a suitable device
shows the bond with that device set as primary slave.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Hello Ryan, 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.ubun
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 n
Hello Ryan, 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.ubun
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 thi
Hello Ryan, 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.ubun
Hello Ryan, 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.ubunt
This bug was fixed in the package systemd - 232-21ubuntu7
---
systemd (232-21ubuntu7) zesty; urgency=medium
* networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
* networkd: add support for ActiveSlave and PrimarySlave netdev options.
(LP: #1709135)
* Cherryp
We got hit by this as well. Some Ceph nodes lost all networking.
--
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/1709135
Title:
add bond primary parameter
Status in nplan
Sounds like maybe that kernel defaults to noarp and we'd want systemd to
retain previous behavior?
Do you have any sysctl configuration that forces arp state?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Actually there is. Before this update, bond interfaces (specifically
802.3ad) were defaulting to ARP enabled. After the upgrade, they are
created with NOARP set on the link.
pre-upgrade:
eth0:
eth1:
bond0:
post-upgrade:
eth0:
eth1:
bond0:
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP
I opened LP #1727301 to track this further
--
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/1709135
Title:
add bond primary parameter
Status in nplan package in Ubuntu:
F
@Markus Schade
Could you please elaborate what you mean? and/or open a new bug with a
tag "regression-updates" describing your system?
In systemd, the patch which was added is as following:
https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/tree/debian/patches/networkd-add-support-to-configu
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20
as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network fil
This bug was fixed in the package systemd - 229-4ubuntu20
---
systemd (229-4ubuntu20) xenial; urgency=medium
* resolved: recognize DNS names with more than one trailing dot as invalid
(LP: #160)
* Ignore failures to set Nice priority on services in containers.
(LP: #17
$ sudo netplan apply
Error in network definition //etc/netplan/bond.yaml line 13 column 8: unknown
key primary
$ dpkg-query -W nplan systemd
nplan 0.23~17.04.1
systemd 232-21ubuntu5
$ sudo netplan apply
$ echo $?
0
$ dpkg-query -W systemd nplan
nplan 0.29~17.04.1
systemd 232-21ubuntu7
Bond
# dpkg-query -W systemd nplan
nplan 0.23~16.04.1
systemd 229-4ubuntu19
# netplan generate
Error in network definition //etc/netplan/bond-primary.yaml line 13 column 8:
unknown key primary
Enabled proposed, retweaked netplan to have correct interface names
# dpkg-query -W systemd nplan
nplan
Hello Ryan, 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.ubun
Hello Ryan, 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.ubunt
Hello Ryan, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
note that one cannot really use bond0 as it will be auto created and
networkd may loose the race to configure it. it is safer to use bond1
until a bugfix is SRUed to set max_bond to zero by default.
pre-tested with artful's netplan on zesty with a backrported systemd.
--
You received this bug no
verification is done for the systemd portion of the bug.
--
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/1709135
Title:
add bond primary parameter
Status in nplan package
Installed nplan 0.29 from artful to get it process the test-case yaml,
to then test networkd portion is working right.
Using:
# cat /etc/netplan/bond-primary.yaml
network:
version: 2
ethernets:
eth0:
match:
name: eth0
dummy0:
match:
driver: dummy
bonds:
** Description changed:
[Impact]
Some complex bond configurations require setting a "primary" interface for
the bond, or setting this greatly improves performance on the network bond.
[Test case]
See below for a configuration example.
1) Apply configuration on a system with netplan.
** Tags added: id-5988c348d036b6f6acb1e389
--
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/1709135
Title:
add bond primary parameter
Status in nplan package in Ubuntu:
F
** Tags added: id-5988c3a877d5e440aecf0c3a
--
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/1709135
Title:
add bond primary parameter
Status in nplan package in Ubuntu:
F
Hello Ryan, 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-4ubuntu20
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Description changed:
[Impact]
Some complex bond configurations require setting a "primary" interface for
the bond, or setting this greatly improves performance on the network bond.
[Test case]
See below for a configuration example.
1) Apply configuration on a system with netplan.
Staged for zesty at: https://git.launchpad.net/~ubuntu-core-
dev/+git/systemd/commit/?id=608838c764f1bce9ad0b506ec40bd15a7df3bcc8
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Released => Triaged
** Changed in: systemd (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: sys
** Description changed:
+ [Impact]
+ Some complex bond configurations require setting a "primary" interface for
the bond, or setting this greatly improves performance on the network bond.
+
+ [Test case]
+ See below for a configuration example.
+ 1) Apply configuration on a system with netplan.
This bug was fixed in the package nplan - 0.26
---
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)
* Au
Sounds like we'd need to add a key under parameters: for the bond
device, as per the original description (but the device needs to be
listed in 'interfaces', and exist in the list of interfaces defined in
netplan:
ethernets:
version: 2
ethernets:
eth0:
match:
driver: virtio
36 matches
Mail list logo
