Public bug reported:
Together with fix for:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1869751 (FTBFS)
This bug will also backport/cherrypick fixes released after 2.0.3
release:
c1bc0a7f4 Merge pull request #2023 from kgaillot/fixes
f00d1120f Merge pull request #2005 from
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.
I have marked Disco was won't fix as it was
As Paride mentioned, this is already fixed in Eoan and Focal and was an
issue for Disco.
** Also affects: pacemaker (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: pacemaker (Ubuntu Eoan)
Importance: Undecided
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
** Also affects: pacemaker (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: pacemaker (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: pacemaker (Ubuntu Disco)
Assignee: Rafael David Tinoco
This merge will solve:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383
** Description changed:
- ClusterLabs released resource-agents v4.5.0 right after our freeze for Focal:
+ # Feature Freeze Exception - resource-agents
-
+ [Proposed Changes]
+ * Merge
commit 92c49b6f2847546f3f938b10a2a97021774f0be3
Author: Jan Pokorný
Date: Wed Dec 4 14:36:59 2019 +0100
IPaddr2: ipt_CLUSTERIP "iptables" extension not "nft" backend
compatible
Reference:
https://lists.clusterlabs.org/pipermail/users/2019-December/026674.html
(thread also
** Changed in: resource-agents (Ubuntu Focal)
Status: Confirmed => New
** Changed in: resource-agents (Ubuntu Focal)
Importance: Wishlist => Undecided
** Changed in: resource-agents (Ubuntu Focal)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Summary changed:
For pacemaker, this is a duplicate of:
https://bugs.launchpad.net/bugs/1439649
So, instead of marking it as duplicate, since it had charm work, I'm
removing pacemaker from the bug and leaving this comment:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/comments/20
"""
>From
>From Corosync 2.4.1 Release Notes:
This release contains fix for one regression and few more smaller fixes.
"""
During 2.3.6 development the bug which is causing pacemaker to not work after
corosync configuration file is reloaded happened. Solution is ether to use this
fixed version
** Also affects: pacemaker (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: pacemaker (Ubuntu Bionic)
Hello Jeff,
I just synced with other engineers about this particular bug and it was
brought to my attention that a MIR was attempted before and didn't pass
(LP: #1854181). Unfortunately, for this case, a MIR is needed because
the package is in [universe].
There is something else:
$ rmadison
*** This bug is a duplicate of bug 1869751 ***
https://bugs.launchpad.net/bugs/1869751
** This bug has been marked a duplicate of bug 1869751
[focal] pacemaker FTBFS because of deprecated ftime()
--
You received this bug notification because you are a member of Ubuntu
Server, which is
13 matches
Mail list logo
