[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
Based upon discussion, we will not be fixing this in Trusty. Updating the SysV scripts to be more error-proof is itself error-prone. Additionally, corosync on Trusty has not received significant updates, and this update itself would lead to at least an additional outage (in order to put the fix into place). If, in the future, an additional security/bugfix update was to be applied to Trusty for corosync, we should revisit this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1748210] Re: Sync haproxy 1.8.3-1 (main) from Debian experimental (main)
It looks like this can become a sync indeed. I'm testing a package I built on this ppa: https://launchpad.net/~ahasenack/+archive/ubuntu/haproxy-18-merge-1748210/+packages It still has the "ubuntu" suffix, just because that's what I arrived at after doing the merge, but it has no delta. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1748210 Title: Sync haproxy 1.8.3-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1748210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
