[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
Dan Streetman
dan.streetman at canonical.com
Wed Oct 2 07:12:29 UTC 2019
> I just tested it on Eoan, using systemd 242-6, and the valid__lft and
preferred_lft did indeed change to 'forever'.
well that's interesting...I tested with the latest upstream systemd code
and i *was* able to reproduce the problem...maybe something reverted the
fix since 242. Unless, of course, I messed up my test :-) I'll
backport the fix for that and see if it fixes bionic, then retest the
latest upstream to make sure it hasn't reverted.
> The discussion in the GitHub issue was rather interesting as well. I
kind of "agree" that this is a strange thing to do, but I don't think
that should be any of systemd's business..
yes, I agree, and it is an entertaining discussion on what systemd
should prevent users from doing ;)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1833193
Title:
systemd-networkd fails to apply static IPv4 when the static IP is the
same as previously configured by DHCP
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
New
Bug description:
In bionic, running systemd 237-3ubuntu10.22 and netplan.io
0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
interface with a static IPv4 address if the statically confiugred
address is the same as the interface already has gotten from DHCP.
This will cause the interface to loose its IP address when the DHCP
lease exires, even though you've told netplan to configure it as
static.
I expect systemd-networkd to actually configure an IP address as
static, regardless of what address the interface has before from DHCP.
# lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
# apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10.22
# apt-cache policy netplan.io
netplan.io:
Installed: 0.97-0ubuntu1~18.04.1
A paste of systemd-networkd's debug log when I run "netplan apply" and
the interface already has the static IP configured from DHCP.
It seems like upon a restart, systemd-networkd will allways add
whatever IP config it had before the service stopped, and then apply
changes (if any). Since my new config has the same IP as it already
had, it does nothing even though the new config has static
configuration.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions
More information about the foundations-bugs
mailing list