** Also affects: corosync (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Medium
Assignee: guessi (guessi)
Status: In Progress
** Changed in: corosync (Ubuntu Focal)
Assignee: guessi (guessi) => (unassigned)
** Changed in: corosync (Ubuntu Focal)
Importance: Medium => Undecided
** Changed in: corosync (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: corosync (Ubuntu Disco)
Status: New => Won't Fix
** Changed in: corosync (Ubuntu Focal)
Status: In Progress => Triaged
** Changed in: corosync (Ubuntu Eoan)
Status: New => Triaged
** Changed in: corosync (Ubuntu Xenial)
Status: New => Triaged
** Changed in: corosync (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to corosync in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
