I assigned to myself to address comment #1 from Robie and try to bump needed values from the test itself. I'll test in an armhf environment just to make sure its good. This will unblock:
https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses_by_team.html#ubuntu-server pacemaker (1.1.18-2ubuntu1 to 2.0.1-4ubuntu1) in proposed for 56 days - pacemaker/2.0.1-4ubuntu1: armhf (log, history) And as soon as corosync is unblocked because of libknet1 MIR, we will be good for corosync and pacemaker. ** Changed in: pacemaker (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: corosync (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- 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
