As discussed in
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074 and
pointed out in
https://bugs.launchpad.net/ubuntu/bionic/+source/keepalived/+bug/1815101/comments/65,
as KeepConfiguration= is part of systemd nowadays, and since the
keepalived fix is available since 2.x, This
Closing bionic as per
https://bugs.launchpad.net/netplan/+bug/1815101/comments/59 (it is also
on EOSS).
** Changed in: keepalived (Ubuntu Bionic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
netplan uses the "networkctl reload/reconfigure" commands nowadays,
instead of hard restarting systemd-networkd:
https://github.com/canonical/netplan/pull/200
This change was activated in v0.104 in the Distro, which landed in Jammy
and is currently being SRUed to Focal and Impish (LP: #1964481).
This bug was fixed in the package systemd - 237-3ubuntu10.51
---
systemd (237-3ubuntu10.51) bionic; urgency=medium
* Add support to keepconfiguration (LP: #1815101)
- lp1815101-0001-add-macro-if-flags-are-set.patch
-
systemd reaches day 7 wo/ autopkgtest failure nor negative
outcome/feedbacks.
I have asked 'sil2100' to promote the package into bionic-updates.
Stay tuned ...
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Maanus for all the testing. Much appreciated.
I'll take care of the rest in a couple of days with Lukasz.
Package needs to stay in proposed for a couple more days (minimum 7 days)
- Eric
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
I installed the package from bionic-proposed and performed the test
cases using keepalived - VIP is not lost. This resolves it.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Hi Maanus,
Would you mind perform the 'test cases' now against the systemd's
bionic-proposed package ? And report any outcome.
This is one of the last steps for Lukasz to approve the proposed package
after the baking minimum aging period (7 days) in verification phase.
- Eric
--
You received
Since the changeset is composed from multiple patches, please be sure to
execute both the test cases mentioned in the Test Case section. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Hello Leroy, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.51 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thank you Dan and Eric!
Summarizing howto with bionic for myself:
Upgrade systemd to the version with "keepconfiguration" fix.
Look at /run/systemd/network/*.network filename, in my example it is
"10-netplan-ens160.network"
Make a directory adding ".d" to this name:
Uploaded into bionic upload queue, now waiting for SRU approval.
- Eric
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because
I've tested 237-3ubuntu10.50+testpkg20210802b3 the ppa and it resolves
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks
> The "default bionic install" uses only netplan yaml and
/etc/systemd/network/ is empty.
yes, but netplan creates .network config files named in a deterministic
way so you know what the name of the networkd file it creates will be. I
don't think netplan currently has a mechanism to include keep-
The "default bionic install" uses only netplan yaml and
/etc/systemd/network/ is empty.
If I switch to systemd.network style, I have to create config files from
scratch anyway and then this KeepConfiguration helps. (Of course I do
not need to keep the netplan yaml after enabling systemd-networkd,
Good catch Dan.
Maanus could you repeat the testing with what Dan brought up ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived,
> Now I need to have IP and gateway in two files - /etc/netplan/01-netcfg.yaml
> and
> /etc/systemd/network/10-netplan-ens160.network
to clarify, don't do that, you should create a systemd-networkd 'drop-
in' instead of copying/modifying the file.
For example, if the networkd config filename
Thanks @Maanus.
So the outcome is positive here then.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
I am using netplan - default in bionic.
I added the repo, made update and reboot.
'systemctl restart systemd-networkd' resulted with keepalived VIP lost.
I added following file and rebooted:
/etc/systemd/network/10-netplan-ens160.network :
---
[Match]
Name=ens160
[Network]
@maanus, That is a first iteration.
sudo add-apt-repository ppa:slashd/keepconfiguration
sudo apt-get update
Let me know the outcome.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
I want to test it in Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases
Any volunteer to test a package in Bionic in the attempt to support
keepconfiguration ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks
> > i'm inclined to also mark this as wont-fix for bionic, unless there are
> > still people affected
by this problem using bionic without some other workaround.
> What kind of workarounds for binoic does this refer to? I have not found any
> reliable workarounds
yet at least.
+1. I did
> i'm inclined to also mark this as wont-fix for bionic, unless there
are still people affected by this problem using bionic without some
other workaround.
What kind of workarounds for binoic does this refer to? I have not found
any reliable workarounds yet at least.
--
You received this bug
For the people on Focal that want to use netplan and keepalived
together: you can just put in an override for the network unit file, to
keep systemd-networkd from touching your interface!
```
$ cat /etc/systemd/network/10-netplan-eno1.network.d/override.conf
[Network]
KeepConfiguration=static
$
i'm marking this as wont-fix for xenial.
i'm inclined to also mark this as wont-fix for bionic, unless there are
still people affected by this problem using bionic without some other
workaround.
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => Won't Fix
** Changed in: systemd
** Changed in: systemd (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd
Dear Eric Desrochers,
I add the PPA into my ubuntu 18.04 corosync/pacemaker service node.
Then I upgrade the following libnss-systemd libpam-systemd libsystemd0 libudev1
systemd systemd-sysv udev package.
But it still failed after re-connect the notwork.
The crmsh show as below:
ERROR:
I have a first iteration of a package:
It's not a final solution nor a long term solution. It is only made to
determine if its fix the problem before considering an SRU: (Ideally one
would test this package in non-production area)
Adding this PPA to your system
sudo add-apt-repository
The above test package has been made for 'systemd' in bionic ^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
Ubuntu HA wise:
I'm recommending all HA clusters to have the cluster interfaces
configured with systemd-networkd DIRECTLY instead of wrapping it through
netplan.io. At least until we're sure that HA has no issues with
netplan.io, having it configured directly will allow us to isolate
possible
** Changed in: systemd (Ubuntu Bionic)
Assignee: Jorge Niedbalski (niedbalski) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@napsty: the "workaround" (from your blog) is actually to use:
- ifupdown/bridge-utils/vlan/resolvconf for network setup OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network
file
Just highlighting it here.
@ddstreet, you said you would try to come up with the
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
-
@napsty: the "workaround" (from your blog) is actually to use:
- ifupdown/bridge-utils/vlan/resolvconf for network setup OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network
file
Just highlighting it here.
@ddstreet, you said you would try to come up with the
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
-
FYI I stumbled on this problem after a system update (which broke
production!) and collected data in a troubleshooting session and
documented this here https://www.claudiokuenzler.com/blog/959
/keepalived-virtual-ip-addresses-gone-lost-after-systemd-update. Once I
found out the restart of
Removing charm-keepalived since I believe no changes are needed there.
It should pick up fixes once they are available on apt archives.
** No longer affects: charm-keepalived
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are
Balint, based on your input...
> thanks for the fixes in Eoan. Unfortunately we have a product based on
> disco and cannot move forward at this time. Being a networking shop,
> this issue has a serious effect on us and we would like to avoid moving
> to something like ifupdown2 within our stable
Balint, based on your input...
> thanks for the fixes in Eoan. Unfortunately we have a product based on
> disco and cannot move forward at this time. Being a networking shop,
> this issue has a serious effect on us and we would like to avoid moving
> to something like ifupdown2 within our stable
** Also affects: heartbeat (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: keepalived (Ubuntu
** Also affects: heartbeat (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: keepalived (Ubuntu
Hi all,
thanks for the fixes in Eoan. Unfortunately we have a product based on
disco and cannot move forward at this time. Being a networking shop,
this issue has a serious effect on us and we would like to avoid moving
to something like ifupdown2 within our stable branch.
For our users the real
Can we backport the fixes to Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface
as disco reaches EOL next week, marking this as wontfix for disco.
** Changed in: systemd (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: keepalived (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
Flagging this as wont fix as heartbeat is already being kept just for
historical reasons (and systemd-networkd can workaround that by the fix
we're backporting to it: KeepConfiguration .service file stanza).
** Changed in: heartbeat (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco)
(k)rafaeldtinoco@kcluster01:~$ dpkg -l | grep "ii systemd "
ii systemd243-3ubuntu1amd64system and service manager
k)rafaeldtinoco@kcluster01:~$ for name in kcluster01 kcluster02
kcluster03; do ssh $name "dpkg -l | grep systemd "; done | grep "ii
systemd "
ii systemd
Hello Leroy, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[impact]
- ip addresses managed by keepalived are lost across networkd restarts
+ - ALL related HA software has a small problem if interfaces are being
+ managed by systemd-networkd: nic restarts/reconfigs are always going to
+ wipe all interfaces aliases when HA
** Description changed:
+ [impact]
+
+ ip addresses managed by keepalived are lost across networkd restarts
+
+ [test case]
+
+ see original description below
+
+ [regression potential]
+
+ this backports KeepConfiguration parameter, which adds some significant
+ complexity to networkd's
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/systemd/+git/systemd/+merge/374027
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master]
Eoan SRU:
MR:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/systemd/+git/systemd/+merge/374027
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1815101
Add:
KeepConfiguration=static
to .network file to keep aliases to.
--
You received this bug notification because you
Test Case:
(k)rafaeldtinoco@kcluster03:~$ crm status
Stack: corosync
Current DC: kcluster02 (version 2.0.1-9e909a5bdd) - partition with quorum
Last updated: Thu Oct 10 17:13:19 2019
Last change: Thu Oct 10 17:11:48 2019 by root via cibadmin on kcluster01
3 nodes configured
5 resources
(k)rafaeldtinoco@kcluster01:~$ sudo vi /etc/systemd/network/10-netplan-
eth3.network
(k)rafaeldtinoco@kcluster01:~$ systemctl restart systemd-networkd
(k)rafaeldtinoco@kcluster01:~$ ip addr show eth3
5: eth3: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether
@ed,
I just finished the backport to Eoan it was straightforward, I'll finish
tests tomorrow with HA related software and networkd enabled HA
clusters. After that I'll give you a better estimation about Disco and
Bionic.
This is the total size of changes (systemd-networkd-tests.py is not so
** Also affects: charm-keepalived
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived,
Thanks Rafael/Christian,
I see that all those patches are in 243 and Eoan is currently on 242
(albeit -6 but i dont think any are already backported) so we'll need to
get this backported all the way down to Bionic.
max@power:~/git/systemd$ _c=( 7da377e 95355a2 db51778 c98d78d 1e49885 )
If you are lazy to look for these commits, feel free to use these links
https://github.com/systemd/systemd/commit/7da377ef16a2112a673247b39041a180b07e973a
https://github.com/systemd/systemd/commit/95355a281c06c5970b7355c38b066910c3be4958
The commits bellow implement support to "keep configuration":
commit 1e498853a39b46155cb89b5c9e74ecb27aaba3ed
Author: Yu Watanabe
Date: Mon Jun 3 01:21:13 2019
test-network: add tests for KeepConfiguration=
commit c98d78d32abba6aadbe89eece7acf0742f59047c
Author: Yu Watanabe
Date: Mon
** Summary changed:
- [master] Restarting systemd-networkd breaks keepalived clusters
+ [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync,
pacemaker (interface aliases are restarted)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
64 matches
Mail list logo