Sigh indeed. The ignoring of this bug report (and many other bad, bad
decisions for that matter) has now lead us to just abandon Ubuntu
entirely. Even for non-server desktop use cases. I have no idea if the
original reported issue has ever actually been dealt with, and I guess I
never will.
--
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
[Expired for ifupdown (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
Sigh.
After I push my /etc/network/interfaces from ansible (not the stub one I
previously posted) - "something" is re-reading it and applying settings.
This never happened in 16.04 until an ifup/ifdown, service restart or
reboot (which is what I expect and need). Not quite sure how to find
the
So from the troubleshooting and testing I just did, it seems like (at
least) I had to do the following:
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
and
mv
Looking for an update on this - specifically the seemingly unanswered
question of "does removing all netplan related config render systemd-
netword 'toothless'". I too am very concerned that simply installing
ifupdown doesn't by itself achieve the result that seems to be put forth
by the various
> A simple "apt install ifupdown" will not undo everything that
installer has done to setup the system, nor redo it for the alternative
networking management tool. Where do you expect ifupdown configs to
materialize from?
Well that's kind of my point - your documentation is deficient around
that.
Please provide the contents of /etc/netplan on the affected systems, and
please let me know, if removing files in said directory makes networkd
ignore interfaces.
Please provide output of $ networkctl
By default, if there is no netplan configuration, networkd does not
"force use of
@wes234234
A simple "apt install ifupdown" will not undo everything that installer
has done to setup the system, nor redo it for the alternative networking
management tool. Where do you expect ifupdown configs to materialize
from? And how do you expect the netplan configs be removed? Given that
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
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/1771236
Title:
forced use of systemd-networkd interferes
There are plenty of examples, some of them bespoke 3rd party things. An
equally large issue though are legacy technicians who aren't familiar
with systemd's way of doing things yet (I've been trying to get them up
to speed though).
But the crux is if returning to ifupdown is offered as an
What is the legacy software in question?
Why does it have pre-up / post-up scripts and what do they do?
Can the functionality be replicated using networkd-dispatcher which is
available out of the box on bionic? Specifically the routable.d/ off.d/
directories. See
Please note, that networkd most likely is triggered by netplan
configuration. If you do not wish an interface to be managed by netplan,
please check netplan configs in /etc/netplan/
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Well I think it pertains to ubuntu's architecture in general not just
systemd but whatever.
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
14 matches
Mail list logo
