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 /etc/netplan/50-cloud-init.yaml /etc/netplan/50-cloud-
init.yaml.disabled
Before taking these two steps, I kept getting a DHCP address on my
interface. After doing this and rebooting, I finally have an interface
that is simply "UP" - as configured in my /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
auto ens160
iface ens160 inet manual
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1771236
Title:
forced use of systemd-networkd interferes with ifupdown in 18.04
Status in ifupdown package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
For several reasons, we are not able to use netplan nor systemd-
networkd due to legacy applications that expect ifupdown's pre-up and
post-up script mechanism. The documentation around 18.04's
(premature, I feel) wholesale adoption of netplan claims that one can
revert to old behaviour by merely installing ifupdown (amongst
assertions that netplan will never offer a mechanism for configuring
pre-up and post-up actions even for network managers that support
them).
However when ifupdown is installed, systemd-networkd still tries to
manage interfaces. If you 'systemctl disable systemd-networkd', upon
next reboot it is automatically re-enabled. We tried disabling any
systemd units even remotely related to networking and yet systemd-
networkd still runs. If it hasn't been configured, it tries to DHCP.
On networks that don't provide DHCP this results in a stupendously
long stall during boot. Currently it appears to be impossible to tell
systemd-networkd not to run in a clean manner that won't get reverted
on package upgrades.
I sincerely hope this is is a bug/oversight and not intentional. We
need to be able to disable systemd-networkd properly.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
