Therefore I'd suggest to:
- add this to server-next to backport just the fix
- look for someone to work on it this Wednesday.
- Set importance high
@Lucas - please have a look if you agree and if you do set these status entries as suggested.
@Jason - for an SRU [1] we will also eventually need a testcase. Do you happen to know if there is some trivial setup plus (I assume) forcing high pid numbers is enough to test this. If so it would be very useful to add these "how to test this on a fresh system" steps here.
From just a glimpse to me 2.0.20 looks too much of a not-just-fixes release for an MRE at: /www.keepalived .org/changelog. html
https:/
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 this Wednesday.
- Set importance high
@Lucas - please have a look if you agree and if you do set these status entries as suggested.
@Jason - for an SRU [1] we will also eventually need a testcase. Do you happen to know if there is some trivial setup plus (I assume) forcing high pid numbers is enough to test this. If so it would be very useful to add these "how to test this on a fresh system" steps here.
[1]: https:/ /wiki.ubuntu. com/StableRelea seUpdates