Thanks for the investigation. I agree with your assessment Christian,
backport only the fix seems to be the way to go.
I'll be trying to define a test case for this SRU based on the info we
already have.
Adding server-next tag and setting the importance to high.
** Changed in: keepalived (Ubuntu
Here are both of the keepalived configs, Both after about as basic as
they get. I am not sure how to force the high pid's. If you need more
information from me, just let me know.
primary keepalived config (update ips to match your environment)
```
# Global Settings for notifications
global_defs {
From just a glimpse to me 2.0.20 looks too much of a not-just-fixes release for
an MRE at:
https://www.keepalived.org/changelog.html
But not reaching qorum on some PIDs seems severe.
Therefore I'd suggest to:
- add this to server-next to backport just the fix
- look for someone to work on it thi
Thanks for the report Jason!
This is fixed in:
https://github.com/acassen/keepalived/commit/23a5b8113bf0b8ec4718443df0406882e8e4d831
Which is in 2.1.0 and later as well as in the 2.0.20 backport.
Thereby >=Impish are fixed already:
keepalived | 1:2.0.19-2ubuntu0.1 | focal-updates| sou
