Public bug reported:
Apart from fixes for:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684
This bug will also backport/cherrypick the following post release fixes:
-> c631951e icmap: icmap_init_r() leaks if
** Description changed:
Together with fixes for:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684
This bug will also backport/cherrypick the following post release fixes:
- -> c631951e icmap:
** Description changed:
- Apart from fixes for:
+ Together with fixes for:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684
This bug will also backport/cherrypick the following post release fixes:
->
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, other
Fix was already included in current pacemaker version by patch:
commit fcfe6fe522138343e4138248829926700fac213e
Author: Yan Gao
Date: Mon Oct 17 11:19:01 2011 +0800
Medium: crmd: Send out all of the meta parameters to lrmd for stop
actions
So I'm flagging this as "Fix Released" as it
*** This bug is a duplicate of bug 1052449 ***
https://bugs.launchpad.net/bugs/1052449
** This bug has been marked a duplicate of bug 1052449
corosync hangs due to missing pacemaker shutdown scripts
--
You received this bug notification because you are a member of Ubuntu
Server, which is
BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
** Changed in: corosync (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Changed in: corosync (Ubuntu)
Status: Confirmed => 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/1869622
Title:
[focal] corosync v3.0.3 last upstream fixes
To
** No longer affects: kronosnet (Ubuntu Focal)
--
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/1866385
Title:
[focal] kronosnet need fixes from just released upstream version
To manage
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/kronosnet/+git/kronosnet/+merge/381356
** Merge proposal linked:
The mentioned patch is the following one:
commit fc03be02bf3a045babfe8233cbc99227da71d024
Author: David Vossel
Date: Fri Jun 29 11:24:52 2012 -0500
High: pengine: cl#5072 - Fixes monitor op stopping after rsc
promotion.
and was supposed to be applied to Precise.
** Also affects:
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.
It is unfortunate that we were unable to
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.
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.
It is unfortunate that we were unable to
For the 2 fixes:
LP: #1437359
LP: #1677684
I have submitted to upstream the following merge request:
https://salsa.debian.org/ha-team/corosync/-/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
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.
It is unfortunate that we were unable to
Public bug reported:
Taking LP: #955164 by example... all resource agents should have resolvable
binary PATHs by default. This bug is opened so all resources can be checked
and fixed appropriately.
Examples:
$ crm_resource --list-standards
ocf
lsb - /etc/init.d/*
service - (sysv +
I'm marking Precise and Trusty as affected.
The suggested fix is currently implemented by Xenial already:
mcp/pacemaker.in:
...
# Required-Start: $network corosync
# Should-Start: $syslog
# Required-Stop:$network corosync
...
** Also affects: pacemaker (Ubuntu Precise)
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu Trusty)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: pacemaker (Ubuntu)
Importance: Medium =>
19 matches
Mail list logo
