I'm closing up corosync / corosync-* bugs for Focal and will check sysv
script tomorrow. For now, I can say that:
(c)rafaeldtinoco@clusterdev:~$ sudo systemctl status corosync-qdevice
● corosync-qdevice.service - Corosync Qdevice daemon
Loaded: loaded
Hello Bert,
We are not yet fully disabling sysv related scripts because there are
systems that are not, yet, using systemd. Not for this case, but, one of
these examples is windows WSL environment, where systemd is not
supported yet. Just wanted to mention this to show there are some other
things
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
Unfortunately this bug is old for us to
This issue still exists and should be fixed. I'm putting together with
some other SRUs so all of them are done at once. Thanks @niedbalski for
bringing up this issue. I'll fix Ubuntu Focal for now and try to get
along with the needed SRUs.
** Changed in: corosync (Ubuntu Trusty)
Assignee:
(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
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a
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
>From upstream documentation:
"""
Pacemaker used to obtain membership and quorum from a custom Corosync plugin.
This plugin also had the capability to start Pacemaker automatically when
Corosync was started. Neither behavior is possible with Corosync 2.0 and beyond
as support for plugins was
** 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
Currently corosync is started by default with a single node ring formed
with localhost:
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ systemctl status
corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Trusty)
Status: New => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: corosync (Ubuntu)
Assignee: Joao
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
Judging by the existing comments, and the
Correct flag for this bug is: Fix Released
per upstream fix:
commit d3b983953d43dd17162be04de405d223fb21cd26
Author: Angus Salkeld
Date: Wed Nov 24 14:35:56 2010 +1100
Add totem/interface/ttl config option.
This adds a per-interface config option to
adjust the TTL.
Currently we have:
if [ "$RUN_ARBITRATOR" != "yes" ]; then
log_warning_msg "To run $DESC, please set RUN_ARBITRATOR to
'yes' in /etc/default/booth"
log_end_msg 0
exit 0
fi
# in eoan:
>> - For 20.04 we really should consider going ahead to the much newer 1.5.2
>> => https://github.com/maxmind/MaxMind-DB-Reader-python/releases
>> @andreas will you take a look at this, just as you did with the other
>> related package that was slightly outdated?
> FFe bug for the update:
Trying to hint this as a force-badtest in britney. Whenever this is
solved, please remove force-badtest.
--
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/1868108
Title:
[autopkgtest][focal]
Upstream issue:
https://github.com/ruby-gnome/ruby-gnome/issues/1389
--
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/1868108
Title:
[autopkgtest][focal] ruby-gnome/3.4.1-2build1
Public bug reported:
ruby-gnome/3.4.1-2* package fails with:
2020-03-19T13:29:50+00:00: Running test for
/tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk
19 matches
Mail list logo