** Changed in: corosync (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: corosync (Ubuntu Bionic)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm agree with you Robie... as I made the change bug 1677684, I'm
dropping this. Sorry for the inconveniences.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is
** Merge proposal unlinked:
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/409319
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is
Using an alternate init system isn't supported on Ubuntu. We support
systemd only. Therefore I'm not sure this bug qualifies for an SRU.
Is there any case where a user using systemd would be affected by this
bug?
Given the triviality of the fix, maybe we can accept it anyway given
it's already
** Description changed:
+ [Impact]
+
+ Users that use the sysv services provided by corosync-notifyd and corosync
packages
+ may find a corosync-notifyd service's misfunction because it uses the pid
file
+ created by corosync service.
+
+
+ [Test Plan]
+
+ In a new VM with bionic
Xenial is now in Extended Security Maintenance (ESM) and this bug
doesn't qualify for it, so this bug will not be fixed for that release.
** Changed in: corosync (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/409319
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is
** Changed in: corosync (Ubuntu Bionic)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: corosync (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still impacting corosync version 2.4.3-0ubuntu1.2 present in
Bionic. As described by Rafael this is affecting only non-systemd users
which seem to be the minority of our users, so I am setting the
importance to Low in Bionic.
** Changed in: corosync (Ubuntu Bionic)
Importance:
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/396608
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/396608
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: corosync (Ubuntu Eoan)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications about
This bug was fixed in the package corosync - 3.0.3-2ubuntu2
---
corosync (3.0.3-2ubuntu2) focal; urgency=medium
[Jorge Niedbalski]
* d/control: corosync binary depends on libqb-dev (LP: #1677684)
[Rafael David Tinoco]
* debian/corosync-notifyd.init: fix for 2 PIDFILEs
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/381355
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications about
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD
diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init
index c908618..837e48a 100644
--- a/debian/corosync-notifyd.init
+++ b/debian/corosync-notifyd.init
@@ -21,7 +21,6 @@ NAME=corosync-notifyd
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD
diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init
index c908618..837e48a 100644
--- a/debian/corosync-notifyd.init
+++ b/debian/corosync-notifyd.init
@@ -21,7 +21,6 @@ NAME=corosync-notifyd
Okay, this is a very simple fix but it is tricky... mainly because ..
possibly 99% of the users of this package are using systemd and the
corosync service unit file... which does not face this issue. I'm not
entirely sure a SRU is the right thing to do on all affected Ubuntu
versions (Xenial,
Okay, this is a very simple fix but it is tricky... mainly because ..
possibly 99% of the users of this package are using systemd and the
corosync service unit file... which does not face this issue. I'm not
entirely sure a SRU is the right thing to do on all affected Ubuntu
versions (Xenial,
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Triaged
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Triaged
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
For the sysv script this still exists...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications about
** Changed in: corosync (Ubuntu)
Status: New => Triaged
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
27 matches
Mail list logo
