** 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
High Availability Team, which is subscribed
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
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
High Availability Team, which is subscribed to
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync,
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
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
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
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
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
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync,
** 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
High Availability Team, which is subscribed to keepalived in Ubuntu.
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
(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
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
@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
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting
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
High
26 matches
Mail list logo
