please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713226
Title:
systemd-networkd messes up
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (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/1713226
Title:
s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (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/1713226
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nplan (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/1713226
Title:
syst
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/1713226
Title:
sy
The example 2 in my first posting is not an bug since the package
contains /lib/systemd/network/80-container-host0.network. As I wrote
this only affects systemd-nspawn containers
the unexpected "thing" is that when you upgrade you do not expect a
system wide configuration that is active in paralle
Here are the files of the networkmanager systemd-networkd conflict (I
already removed ifupdown, the problem is the same, so we say for sure
networkmanager or systemd-networkd causes the problem)
the output of ip a is the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen
@msaxl
for both examples, can you please attach the existing configs for
ifupdown, network-manager, and networkd? As in the contents of
/etc/network/interfaces /etc/NetworkManager and output of udevadm info
on the interface and contents of /etc/systemd/network?
I want to reproduce these bugs and
also, we got new network-manager in artful which may have regressed.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/171322
Steve,
It seems that unconditional enablement and start of networkd in
src:systemd.postinst has side-effects, especially when netwokr-manager
is directly managing desktop systems, without netplan.
I think we should not unconditially enable and start entworkd in
src:systemd.postinst, and instead h
this was a upgrade so the ifupdown problem should not happen with clean
installs.
How is the migration planned?
If for example one will do a upgrade from 16.04 to the next 18.04 such
problems are a clear show stopper since breaking the network for most
servers will mean needing physical access.
Is this on upgrades to artful? or clean-install / clean-bring up of
artful?
Note that artful will no longer have ifupdown installed on clean-install, and
thus /etc/network/interfaces changes for clean-installs will have no effect at
all. And one should instead use netplan e.g. $ sudo netplan ifu
12 matches
Mail list logo
