We have now migrated to systemd, and this bug is pretty old.
Nevertheless, I would like to check again if this condition would ever
happen in new corosync started by systemd and/or the sysv generators (or
if any conflict related to this could exist). Will mark this as Done as
soon as I'm sure (during this new Ubuntu HA work).
** Changed in: corosync (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: corosync (Ubuntu)
Importance: Undecided => Medium
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586876
Title:
Corosync report "Started" itself too early
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1586876/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
