[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-11-04 Thread Frank Heimes
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2 --- network-manager (1.10.6-2ubuntu1.2) bionic; urgency=medium [ Till Kamppeter ] * debian/tests/nm: Add gi.require_version() calls for NetworkManager and NMClient to avoid stderr output which fails the

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-11-02 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu Bionic) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-10-29 Thread Frank Heimes
** Changed in: ubuntu-z-systems Status: Won't Fix => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-10-29 Thread Dan Streetman
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-10-26 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-10-25 Thread Timo Aaltonen
Hello bugproxy, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-06-17 Thread Frank Heimes
Since our focus is on netplan only, I'm changing the status to Won't Fix. ** Changed in: ubuntu-z-systems Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-06-17 Thread Manoj Iyer
** Changed in: network-manager (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-12-18 Thread Sebastien Bacher
The issue looks like it could be what is fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680 (the change is included in 1.10.8 which is currently not yet in bionic but being SRUed) -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-08 Thread Steve Langasek
# uname -a Linux rare-stork 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux # ip -4 addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 3:

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-08 Thread Steve Langasek
sorry, that was with Ubuntu 18.10 host kernel by mistake. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-08 Thread Steve Langasek
Test repeated on an Ubuntu 18.04 s390x container (Ubuntu 18.04 host): # ip -4 addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 6: bond0.100@bond0: mtu 1500 qdisc noqueue state UP

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-07 Thread Steve Langasek
Note that the above test was with Ubuntu 18.04 on x86. With a preliminary test of Ubuntu 18.10 on s390x, the eth0 interface fails to configure at all. I will investigate further on Monday. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-07 Thread Steve Langasek
Here is an example netplan yaml that emulates this configuration in a test container. network: version: 2 ethernets: eth0: dhcp4: false bonds: bond0: interfaces: [eth0] parameters: mode: active-backup

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-07 Thread Steve Langasek
The description for reproducing this says: > 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. > 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). However, the commands you list out

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-09-06 Thread Frank Heimes
** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-08-31 Thread Steve Langasek
This output shows that you are using nmcli to manage network connections. Network-manager is not part of the Ubuntu Server platform, it is not included in the images Ubuntu provides for s390x, and it is not the recommended tool for configuring vlans and bonds in Ubuntu. To show that this is a

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2018-08-31 Thread Dimitri John Ledkov
** Package changed: linux (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto