[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
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 (/lib/systemd/system/corosync-qdevice.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:corosync-qdevice systemd is not defaulting to sysv generator anymore when systemd units are available, as you can see above, package corosync-qdevice installed defaults to systemd unit so having both simultaneously won't be a problem to new users (apart from having a tiny extra file at /etc/init.d/ directory). -- 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/1809682 Title: "systemctl enable corosync-qdevice.service" fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+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
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
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 to be taken in consideration when dropping support, entirely, for
sysv scripts, for example.
Just a quick example on corosync running inside WSL environment:
rafaeldtinoco@lenovo:~$ uname -a
Linux lenovo 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019
x86_64 x86_64 x86_64 GNU/Linux
rafaeldtinoco@lenovo:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
$ sudo corosync -f
Mar 20 01:49:47 notice [MAIN ] Corosync Cluster Engine 3.0.1 starting up
Mar 20 01:49:47 info[MAIN ] Corosync built-in features: dbus monitoring
watchdog augeas systemd xmlconf snmp pie relro bindnow
Mar 20 01:49:47 warning [MAIN ] Could not lock memory of service to avoid page
faults: Function not implemented (38)
Mar 20 01:49:47 notice [TOTEM ] Initializing transport (UDP/IP Unicast).
Mar 20 01:49:47 warning [TOTEM ] Could not set traffic priority: Protocol not
available (92)
Mar 20 01:49:47 notice [TOTEM ] The network interface [127.0.0.1] is now up.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
map access [0]
Mar 20 01:49:47 info[QB] server name: cmap
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
service [1]
Mar 20 01:49:47 info[QB] server name: cfg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster closed
process group service v1.01 [2]
Mar 20 01:49:47 info[QB] server name: cpg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync profile
loading service [4]
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync resource
monitoring service [6]
Mar 20 01:49:47 warning [WD] Watchdog not enabled by configuration
Mar 20 01:49:47 warning [WD] resource load_15min missing a recovery key.
Mar 20 01:49:47 warning [WD] resource memory_used missing a recovery key.
Mar 20 01:49:47 info[WD] no resources configured.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync watchdog
service [7]
Mar 20 01:49:47 notice [QUORUM] Using quorum provider corosync_votequorum
Mar 20 01:49:47 notice [QUORUM] This node is within the primary component and
will provide service.
Mar 20 01:49:47 notice [QUORUM] Members[0]:
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync vote quorum
service v1.0 [5]
Mar 20 01:49:47 info[QB] server name: votequorum
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster quorum
service v0.1 [3]
Mar 20 01:49:47 info[QB] server name: quorum
Mar 20 01:49:47 notice [TOTEM ] adding new UDPU member {127.0.0.1}
Mar 20 01:49:47 notice [TOTEM ] A new membership (1:28) was formed. Members
joined: 1
Mar 20 01:49:47 warning [CPG ] downlist left_list: 0 received
Mar 20 01:49:47 notice [QUORUM] Members[1]: 1
Mar 20 01:49:47 notice [MAIN ] Completed service synchronization, ready to
provide service.
--
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/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+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
[Bug 1340172] Re: [OSCI] Add mamange/unmanage blocks to corosync init scripts
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 consider having an sysv-compatible option to put the cluster into maintenance mode. Corosync is also being managed, for sometime now, by systemd so this particular change wouldn't make much sense. IMHO this type of cluster change should be done by the cluster administrator in specific tools like crmsh, pcs, and not in an init script. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. ** Also affects: corosync (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Precise) Status: New => Incomplete ** Changed in: corosync (Ubuntu) Status: Triaged => Won't Fix ** Changed in: corosync (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu Precise) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu) Importance: High => Undecided -- 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/1340172 Title: [OSCI] Add mamange/unmanage blocks to corosync init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1340172/+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
[Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found
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: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Zesty) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu Xenial) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: corosync (Ubuntu) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Zesty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Trusty) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu Xenial) Importance: Medium => Undecided ** Also affects: corosync (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: corosync (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Eoan) Status: New => Confirmed ** Changed in: corosync (Ubuntu Disco) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Bionic) Status: New => Confirmed ** Changed in: corosync (Ubuntu Zesty) Status: Incomplete => Won't Fix ** Changed in: corosync (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: corosync (Ubuntu Trusty) Status: Incomplete => Won't Fix -- 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/1677684 Title: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb- blackbox: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+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
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
(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 DAEMON=/usr/sbin/$NAME PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME -PIDFILE=/var/run/corosync.pid RARUNDIR=/var/run/resource-agents # Exit if the package is not installed If anyone faces this issue, just remove the second PIDFILE as it appears to be a leftover. I'll fix this and point this out to Debian as it also faces the same issue. NEVERTHELESS, remember that this issue would only exist if you are using the "sysv" scripts OR the sysv-generator (making systemd to control the service through sysv scripts). All others are probably relying in systemd to start/stop/monitor corosync daemon (/lib/systemd/system/corosync.service). -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+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
[Bug 1654403] Re: Race condition in hacluster charm that leaves pacemaker down
** 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 member of Ubuntu Server, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1654403 Title: Race condition in hacluster charm that leaves pacemaker down To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1654403/+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
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
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, Bionic, Eoan). Will discuss this with the server team. Meanwhile, fixing Focal seems appropriate just because its not released yet ... :\ but I'll keep this "on the hand" until I have more fixes so I do the SRU all at once. ** Changed in: corosync (Ubuntu Focal) Status: Triaged => In Progress -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+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
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
** 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 Status: New ** Also affects: corosync (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Focal) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu Disco) Status: New => Won't Fix ** Changed in: corosync (Ubuntu Trusty) Status: New => Won't Fix ** 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 the bug report. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+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
[Bug 1586876] Re: Corosync report "Started" itself too early
>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 removed. Instead, Pacemaker must be started as a separate job/initscript. Also, since Pacemaker made use of the plugin for message routing, a node using the plugin (Corosync prior to 2.0) cannot talk to one that isn’t (Corosync 2.0+). Rolling upgrades between these versions are therefore not possible and an alternate strategy must be used. """ showing that since Ubuntu Trusty this detection behavior is not supported any longer. Nowadays, we start both services separately and using systemd. Corosync starts with a simple one-node only (localhost) ring configured: (c)rafaeldtinoco@clusterdev:~$ systemctl status corosync ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-03-19 20:16:49 UTC; 45min ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 851 (corosync) Tasks: 9 (limit: 23186) Memory: 125.9M CGroup: /system.slice/corosync.service └─851 /usr/sbin/corosync -f (c)rafaeldtinoco@clusterdev:~$ sudo corosync-quorumtool Quorum information -- Date: Thu Mar 19 21:02:21 2020 Quorum provider: corosync_votequorum Nodes:1 Node ID: 1 Ring ID: 1.5 Quorate: Yes Votequorum information -- Expected votes: 1 Highest expected: 1 Total votes: 1 Quorum: 1 Flags:Quorate Membership information -- Nodeid Votes Name 1 1 node1 (local) AND systemd is responsible to guarantee the synchronicity needed. >From pacemaker service unit: ... After=corosync.service Requires=corosync.service ... # If you want Corosync to stop whenever Pacemaker is stopped, # uncomment the next line too: # # ExecStopPost=/bin/sh -c 'pidof pacemaker-controld || killall -TERM corosync' ... # Pacemaker will restart along with Corosync if Corosync is stopped while # Pacemaker is running. # In this case, if you want to be fenced always (if you do not want to restart) # uncomment ExecStopPost below. # # ExecStopPost=/bin/sh -c 'pidof corosync || \ # /usr/bin/systemctl --no-block stop pacemaker' you have different options to control behavior for start/stop and restart accordingly with corosync status. ** Changed in: corosync (Ubuntu Focal) Status: Triaged => Fix Released ** Changed in: corosync (Ubuntu Eoan) Status: Triaged => Fix Released ** Changed in: corosync (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: corosync (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/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
[Bug 1586876] Re: Corosync report "Started" itself too early
** 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
[Bug 1239734] Re: corosync sends first time users on a hunt, simple fix
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 preset: enabled) Active: active (running) since Thu 2020-03-19 20:16:49 UTC; 2min 10s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 851 (corosync) Tasks: 9 (limit: 23186) Memory: 125.7M CGroup: /system.slice/corosync.service └─851 /usr/sbin/corosync -f (c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ sudo corosync-quorumtool Quorum information -- Date: Thu Mar 19 20:19:37 2020 Quorum provider: corosync_votequorum Nodes:1 Node ID: 1 Ring ID: 1.5 Quorate: Yes Votequorum information -- Expected votes: 1 Highest expected: 1 Total votes: 1 Quorum: 1 Flags:Quorate Membership information -- Nodeid Votes Name 1 1 node1 (local) Because we try to make things "easier" (no failure on startups because the lack of configuration files, for example). Of course having a HA cluster is something beyond the scope of this bug and it might require an experienced system administrator to be able to make corosync to work in a meaningful way. Nevertheless, for any future bug readers, may I recommend the following reading: https://discourse.ubuntu.com/t/ubuntu-high-availability-shared-scsi- disk-environments/14874 in order to get a simple, yet supported, cluster configuration in a shared scsi environment. Thanks for reporting this. ** Changed in: corosync (Ubuntu) Status: Triaged => Fix Released ** Changed in: corosync (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) -- 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/1239734 Title: corosync sends first time users on a hunt, simple fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1239734/+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
[Bug 1019833] Re: problem wtih the configuration of the cluster.conf file. when
** 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 (nobrefr) => (unassigned) ** Changed in: corosync (Ubuntu) Importance: Medium => Undecided ** Changed in: corosync (Ubuntu) Status: Fix Released => Invalid -- 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/1019833 Title: problem wtih the configuration of the cluster.conf file. when To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1019833/+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
[Bug 1251298] Re: Failed to sign on to LRMd with Heartbeat/Pacemaker
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 pointed upstream discussion thread, it appears that the wrong lrmd was being set after upgrade and that led existing cluster to confusion when connecting to the local resource manager daemon. It is unfortunate that we were unable to resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. ** Changed in: cluster-glue (Ubuntu) Status: Confirmed => Incomplete ** Also affects: cluster-glue (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: cluster-glue (Ubuntu Trusty) Status: New => Incomplete ** Changed in: cluster-glue (Ubuntu) Status: Incomplete => Fix Released ** Changed in: cluster-glue (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to cluster-glue in Ubuntu. https://bugs.launchpad.net/bugs/1251298 Title: Failed to sign on to LRMd with Heartbeat/Pacemaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1251298/+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
[Bug 637127] Re: TTL is one - prevents multicast routing
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. Signed-off-by: Angus Salkeld Reviewed-by: Steven Dake ** Changed in: corosync (Ubuntu) Status: Incomplete => Fix Released -- 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/637127 Title: TTL is one - prevents multicast routing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/637127/+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
[Bug 1413845] Re: booth.init says to modify /etc/default/boothd, which does not exist
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: rafaeldtinoco@workstation:~/.../debian/booth/debian$ apt-file search booth | grep default booth: /etc/default/booth so I'm marking this as Fix Released because of upstream (Debian) fixes. ** Changed in: booth (Ubuntu) Status: New => Fix Released -- 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/1413845 Title: booth.init says to modify /etc/default/boothd, which does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/booth/+bug/1413845/+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
[Bug 1861101] Re: [MIR]: dependency of bind9
>> - 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: https://bugs.launchpad.net/ubuntu/+source /python-maxminddb/+bug/1867919 FFe approved, MP for the update to 1.5.2 at https://code.launchpad.net/~ahasenack/ubuntu/+source/python- maxminddb/+git/python-maxminddb/+merge/380854 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1861101 Title: [MIR]: dependency of bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1861101/+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
[Bug 1868108] Re: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure
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] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+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
[Bug 1868108] Re: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure
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 class:TestWebKit2GtkWebView failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+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
[Bug 1868108] [NEW] [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure
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 Loaded suite test Started (run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ..[2020-03-19 13:29:52] INFO WEBrick 1.6.0 [2020-03-19 13:29:52] INFO ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu] [2020-03-19 13:29:52] INFO WEBrick::HTTPServer#start: pid=9142 port=37651 (WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files F === Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri): expected but was /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in `block (2 levels) in ' 103: @view.load_uri(http_url) 104: loop.run 105: => 106: assert_true(loaded) 107: end 108: end 109: end ===[2020-03-19 13:30:22] INFO going to shutdown ... [2020-03-19 13:30:22] INFO WEBrick::HTTPServer#start done. .. Finished in 30.95292437 seconds. --- 9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.8889% passed --- 0.29 tests/s, 0.29 assertions/s Failed to run test: webkit2-gtk Failed targets: webkit2-gtk Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or directory) on X server :99. autopkgtest [13:30:22]: test run-test: ---] run-test FAIL non-zero exit status 1 autopkgtest [13:30:23]: test run-test: - - - - - - - - - - results - - - - - - - - - - autopkgtest [13:30:23]: summary run-test FAIL non-zero exit status 1 Exit request sent. When running in ppc64el. This is likely due a timeout in glib main loop for that architecture but can't know for sure. I'm opening this bug so I can blacklist that particular test. ** Affects: ruby-gnome (Ubuntu) Importance: Undecided Assignee: Lucas Kanashiro (lucaskanashiro) Status: Confirmed ** Affects: ruby-gnome (Ubuntu Focal) Importance: Undecided Assignee: Lucas Kanashiro (lucaskanashiro) Status: Confirmed ** Also affects: ruby-gnome (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ruby-gnome (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: ruby-gnome (Ubuntu Focal) Status: New => Confirmed ** Bug watch added: github.com/ruby-gnome/ruby-gnome/issues #1389 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 class:TestWebKit2GtkWebView failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1868108/+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
