Will anything be done here? This basically breaks keepalived for bionic.
I.e, will keepalived >= 2.0.x be available for bionic?
--
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
Public bug reported:
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 in
** Summary changed:
- systemd-network fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
+ systemd-networkd fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
--
You received this bug notification because you are a
I should add that if I set "dhcp4: no" explicit when confiugring static
addressing, it behaves as expected, but according to the current
documentation, this parameter should default to "no", so this should not
be neccescary.
--
You received this bug notification because you are a member of Ubuntu
@ddstreet It seems to work as expected in Eoan!
netplan.io 0.98-0ubuntu1
--
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/1836695
Title:
systemd fails to setup static routes
Repro instructions:
- (Enable systemd-networkd debug logging)
- Start a server with its interface configured with DHCP
- In the netplan config, configure the interface wtih static addressing, using
the exact same address as it already has gotten from DHCP
- Either wait for the initial DHCP lease t
Yes that's the same issue. And it seems to be fixed in some version as
well? I just tested it on Eoan, using systemd 242-6, and the valid__lft
and preferred_lft did indeed change to 'forever'. Don't know which
version it was fixed in though. Do you think it kan be backported to
Bionic?
The discuss
Hi. I did som further investigation here, and I think I've figured out
what happens in networkd here.
Aug 21 10:54:45 nettest1 systemd-networkd[5463]: ens3: Removing address:
2001:700:1d00:ec00:5054:ff:fe49:4bc9/64 (valid for 4w 2d)
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Removing
Hi!
Tested with systemd=237-3ubuntu10.34 from proposed (and
libsystemd0=237-3ubuntu10.34) and it seems to fix the problem.
What's interesting though, is that a fresh install of bionic came with a
newer version (systemd=237-3ubuntu10.38) - which has the bug. This test
effectively ended up in a dow
Hi!
Re-tested with systemd=237-3ubuntu10.39 from proposed (and
libsystemd0=237-3ubuntu10.39), and it works.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Seems like it is fixed now, in the unity package:
$ sudo apt-cache policy unity
unity:
Installert: 7.2.2+14.04.20140714-0ubuntu1.1
See changelog:
https://launchpad.net/ubuntu/+source/unity/7.2.2+14.04.20140714-0ubuntu1.1
And the associated bug:
https://bugs.launchpad.net/ubuntu/+source/unity/
dovercrash: I'm having that issue with chrome as well.
$ sudo apt-cache policy google-chrome-stable
google-chrome-stable:
Installed: 36.0.1985.125-1
Same versions of unity and compiz that you have.
Tried to reproduce it with other applications (gedit, gnome-terminal,
firefox), but it does onl
12 matches
Mail list logo
