I flagged this as high as this is impacting pacemaker migration. After
this being fixed, corosync (depending on libknet1 will still block
migration, but thas has already been address in MIR
https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1811139).
I'm working on this now.
** Changed in: corosync (Ubuntu)
Importance: Medium => High
** Changed in: pacemaker (Ubuntu)
Importance: Medium => High
** Changed in: corosync (Ubuntu)
Status: Triaged => In Progress
** Changed in: pacemaker (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828228
Title:
corosync fails to start in container (armhf) bump some limits
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1828228/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
