*** This bug is a duplicate of bug 1892871 ***
https://bugs.launchpad.net/bugs/1892871
** This bug has been marked a duplicate of bug 1892871
haproxy needs merge with debian experimental 2.2 (LTS version)
--
You received this bug notification because you are a member of Ubuntu
High
020-11100
** Changed in: haproxy (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1892871
Titl
Public bug reported:
Currently Debian experimental is at "2025-Q2 (LTS)" which is the LTS
version for HAPROXY. We should merge this version sooner than later in
the LTS cycles.
** Affects: haproxy (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Thanks for taking care of this Jorge. Let me know whenever you have a
fix ready for this.
Cheers!
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1890491
Title:
A
Forwarded Message
Subject: [ClusterLabs] Coming in Pacemaker 2.0.5: on-fail=demote /
no-quorum-policy=demote
Date: Mon, 10 Aug 2020 11:47:24 -0500
From: Ken Gaillot
Reply-To: Cluster Labs - All topics related to open-source clustering welcomed
Organization: Red Hat
To:
)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1890314
Title:
RFE HAProxy 2.2 for groovy
Sta
** Changed in: haproxy (Ubuntu)
Status: New => Triaged
** Changed in: haproxy (Ubuntu)
Importance: Undecided => Wishlist
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to
This feature is in 2.0.x releases, so SRU for bionic would be out of question:
pacemaker | 1.1.18-0ubuntu1 | bionic | source
pacemaker | 1.1.18-0ubuntu1.1 | bionic-security | source
pacemaker | 1.1.18-0ubuntu1.2 | bionic-updates | source
** Also affects: pacemaker (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1890185
Title:
scheduler:
Public bug reported:
There is a request for the feature:
Feature: scheduler: new on-fail="demote" recovery policy for promoted…
to be backported to Ubuntu LTS versions.
** Affects: pacemaker (Ubuntu)
Importance: Medium
Status: Triaged
** Affects: pacemaker (Ubuntu Bionic)
** Description changed:
- pacemaker - 2.0.3-3ubuntu3 needs update (2.0.4-2)
+ BUG: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1886546
+ PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1886546
+ MERGE:
** Description changed:
BUG:
Public bug reported:
pacemaker - 2.0.3-3ubuntu3 needs update (2.0.4-2)
** Affects: pacemaker (Ubuntu)
Importance: Medium
Status: In Progress
** Changed in: pacemaker (Ubuntu)
Status: New => In Progress
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => Medium
** Changed in: pacemaker (Ubuntu)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pac
*** This bug is a duplicate of bug 1869643 ***
https://bugs.launchpad.net/bugs/1869643
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
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
*** This bug is a duplicate of bug 1869643 ***
https://bugs.launchpad.net/bugs/1869643
** This bug is no longer a duplicate of bug 1412438
OCF:pacemaker:o2cb broken in 14.04
** This bug has been marked a duplicate of bug 1869643
{fence,resource}-agents: PATH for all binaries called by
This bug was fixed in the package ocfs2-tools - 1.8.6-5
Sponsored for Logan Rosen (logan)
---
ocfs2-tools (1.8.6-5) unstable; urgency=medium
* debian/control: limit build to linux architectures
-- Valentin Vidic Thu, 21 May 2020 14:10:56 +0200
ocfs2-tools (1.8.6-4) unstable;
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
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
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
Hello Logan,
I haven't started yet the work of merging and syncing HA packages for
20.10, but will do very soon. Added this to my queue!
Thank you!
** Changed in: ocfs2-tools (Ubuntu)
Status: New => Triaged
** Changed in: ocfs2-tools (Ubuntu)
Assignee: (unassigned) => Rafael
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
-
to come up with the netplan change for
KeepConfiguration. Did you have time to check on this ? (just checking).
Cheers o/
** Changed in: keepalived (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: keepalived (Ubuntu Xenial)
Assignee: Rafael David Tinoco (
** Changed in: pacemaker (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal deploy creates a 'node1' node
Here you will find the autopkgtests for pacemaker:
http://autopkgtest.ubuntu.com/packages/p/pacemaker/focal/amd64
the installation ends with a corosync node online:
Cluster Summary:
* Stack: corosync
* Current DC: node1 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated:
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Ti
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad
** Changed in: heartbeat (Ubuntu)
Status: New => Triaged
** Changed in: heartbeat (Ubuntu)
Importance: Undecided => Medium
** Also affects: heartbeat (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: heartbeat (Ubuntu Xenial)
Status: New => Triaged
**
** Changed in: pcs (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: corosync (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (u
PPA successfully built pacemaker fixes:
https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
and the merge request has been +1.
** Description changed:
- This bug backport/cherrypick fixes released after 2.0.3 release.
- The correct patches are going to be defined within this bug
(Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1869751
Title:
[focal] pacemaker FTBFS beca
** Description changed:
- 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.
+ This bug backport/cherrypick fixes released after 2.0.3 release.
The correct
There is an on-going merge request for this bug.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1870235
Title:
[focal] pacemaker v2.0.3 last upstream fixes
Status in
Check:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1870235
for the fix (same merge request).
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1869751
Title:
Cherry-picks that seem to make sense after 2.0.3 release are:
Fix: tools: Fix definition of curses_indented_printf.
Fix: iso8601: Fix crm_time_parse_offset() to parse offset with plus sign.
Log: libcrmcommon: correctly raise detail log line length
Low: libcrmservice: handle child wait errors
** Description changed:
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
There are other comments saying that the issue does not seem to be
solved:
https://github.com/libstatgrab/libstatgrab/issues/102#issuecomment-509715203
I'm marking this as incomplete since we still need a dump to do anything
further.
** Also affects: libstatgrab (Ubuntu Eoan)
Importance:
While some may think the fix for this is to suppress deprecated warning
OR to "fix" ftime()... the actual fix for this is to start using
MONOTONIC clock for the related functions:
(c)rafaeldtinoco@clufocaldev:~/.../sources/ubuntu/pacemaker$ git diff HEAD
diff --git a/configure.ac b/configure.ac
commit 4b8b84cce1fd57eec1f47ca44780d60c148b399d
Author: Jan Pokorný
Date: Fri Nov 15 16:06:57 2019 +0100
Build: restore buildability in the face of obsolete ftime(3)
Since the usage of ftime(3) is purely optional and since
clock_gettime(3) is mandated with POSIX 2001, we can
comments.
** Affects: pacemaker (Ubuntu)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: pacemaker (Ubuntu)
Status: New => In Progress
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => High
** C
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
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.
I have marked Disco was won't fix as it was
** 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 Tin
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
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
** 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)
*** 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
High Availability
ecided => High
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1869751
Title:
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
** 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 =>
*** 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
High
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
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:
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)
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
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
** Changed in: corosync (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1869622
Title:
[focal] corosync v3.0.3 last
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
High
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
High Availability Team, which is subscribed to corosync in
** 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:
e48120 totemconfig: Free leaks found by coverity = fix
** Affects: corosync (Ubuntu)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: corosync (Ubuntu)
Status: New => Confirmed
** Changed in: corosync (Ubuntu)
Impor
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
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 notif
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
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
High Availability Team, whi
** 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
** 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
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.
e (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/1251298
Title:
Failed to sign on to LRMd wi
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/380336
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
** Description changed:
OBS: This bug was originally into LP: #1865523 but it was split.
SRU: pacemaker
[Impact]
- * fence_scsi is not currently working in a share disk environment
+ * fence_scsi is not currently working in a share disk environment
- * all clusters
SUMMARY:
One using packages from:
https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
in Ubuntu Bionic will be workedaround temporarily (until fixes are
released) for the bugs:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523
** Summary changed:
- [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
+ [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in
** Description changed:
+ OBS: This bug was originally into LP: #1865523 but it was split.
+
+ SRU: pacemaker
+
+ [Impact]
+
+ * fence_scsi is not currently working in a share disk environment
+
+ * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
+ be able to
** No longer affects: pacemaker (Ubuntu)
** No longer affects: pacemaker (Ubuntu Bionic)
** Description changed:
+ OBS: I have split this bug into 2 bugs:
+ - fence-agents (this) and pacemaker (LP: #1866119)
+
SRU: fence-agents
[Impact]
* fence_scsi is not currently
Public bug reported:
OBS: This bug was originally into LP: #1865523 but it was split.
SRU: pacemaker
[Impact]
* fence_scsi is not currently working in a share disk environment
* all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
be able to start the fencing agents
** Description changed:
+ SRU: fence-agents
+
+ [Impact]
+
+ * fence_scsi is not currently working in a share disk environment
+
+ * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
+ be able to start the fencing agents OR, in worst case scenarios, the
+ fence_scsi
# For Ubuntu Bionic:
Okay, after bisecting fence-scsi and monitoring all its functions I was
able to isolate the patches that I need to take to bionic to make it
compatible with existing version and, at the same time, operational:
Note: all tests were conducted with Pacemaker v1.1.19-0ubuntu1
# Demonstration of fence_scsi agent working in Bionic:
(k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo dpkg -i ./*.deb
dpkg: warning: downgrading fence-agents from 4.4.0-2 to 4.0.25-2ubuntu1
(Reading database ... 85434 files and directories currently installed.)
Preparing to unpack
Now I'm going to work with this package and check needed Pacemaker
fixes. After that I'm going to propose both merges together.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
# Demonstration of fence_scsi fencing a node:
(k)rafaeldtinoco@clubionic03:~/.../upstream$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
# iscsi
auto eth1
iface eth1 inet static
address 10.250.1.12/24
# private
auto eth2
iface eth2 inet static
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/379581
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/379595
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/379595
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
Public bug reported:
Package: pacemaker (debian: 2.0.3-3, ubuntu: 2.0.1-5ubuntu5) needs merge
** Affects: pacemaker (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: pacemaker (Ubuntu)
Status: New
/quorumtool: skip if memlock can't be set to unlimited by uid 0
-- Rafael David Tinoco Thu, 20 Feb 2020
17:57:22 +
corosync (3.0.3-2) unstable; urgency=medium
* [d0a06e5] Separate the autopkgtests and make them generate artifacts
* [8680d48] Run Salsa CI reprotest with diffoscope
Public bug reported:
Package: corosync (debian: 3.0.3-2, ubuntu: 3.0.2-1ubuntu2) needs merge
** Affects: corosync (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: corosync (Ubuntu)
Status: New => In Progr
cts: fence-agents (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: fence-agents (Ubuntu)
Status: New => Confirmed
** Changed in: fence-agents (Ubuntu)
Importance: Undecided => Medium
** Changed in: fenc
https://salsa.debian.org/ha-team/pacemaker/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1863437
Title:
[focal] pacemaker i386 should drop a few i386
Upstream already had the following commit (since @vorlon opened the bug
in January):
commit 543574f18
Author: Ferenc Wágner
Date: Thu Jan 9 14:19:19 2020
Omit pacemaker{, -cli-utils, -remote} on Ubuntu/i386
Closes: #948379
diff --git a/debian/rules b/debian/rules
index
Merged and uploaded.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1863437
Title:
[focal] pacemaker i386 should drop a few i386 only packages
Status in pacemaker
"fakeroot debian/rules build-arch" gives me:
dpkg-deb: building package 'pacemaker-remote' in
'../pacemaker-remote_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'pacemaker' in
'../pacemaker_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'libcrmcluster29' in
# i386 build in local environment
dpkg-deb: building package 'libcib27' in '../libcib27_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'pacemaker-common' in
'../pacemaker-common_2.0.1-5ubuntu5_all.deb'.
dpkg-deb: building package 'libcrmcommon34' in
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Affects: pacemaker (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: pacemaker (Ubuntu)
Status: New =&
1 - 100 of 323 matches
Mail list logo
