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

Reply via email to