I've used your git-ubuntu branch to generate the source package and
upload it. You (server team) will have to break this merge into the 3
commits again during next merge with upstream (debian) as I did not have
permission to upload to pkg/ubuntu/devel (not sure why).
$ dput ubuntu
Applying patch 0004-allow-non-root-usage.patch
patching file src/liboping.c
Hunk #2 succeeded at 1669 (offset -1 lines).
Refreshed the patch, generated src package, all good, patch fixes the
issue.
$ dput ubuntu liboping_1.10.0-1ubuntu0.1_source.changes
Checking signature on .changes
gpg:
We don't, like we've spoken on IRC. Thanks a lot for the information. I
missed the SRUs and I'm very glad they were done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949286
Title:
[MIR]: Include
** Changed in: dwarves-dfsg (Ubuntu Bionic)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After this MIR, the kernel HWE source code will have to use "pahole-btf"
tool to do the BTF encoding in the HWE kernel builds from then on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949286
I have placed a MIR for "pahole-btf" package (a backport of Impish's
dwarves-dfsg package to Bionic and Focal) at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949286. This way,
the kernel builds may depend on "pahole-btf" binary package, from main,
and finally include BTF debug
The proposed package is at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/pahole-btf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949286
Title:
[MIR]: Include dwarves-dfsg-hwe package
** Description changed:
This is a follow-on request of bug:
HWE kernels should support eBPF CO-RE
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
[Availability]
- Package is already available in all Ubuntu versions.
- This is a backported version (Impish) to
Public bug reported:
This is a follow-on request of bug:
HWE kernels should support eBPF CO-RE
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926330
[Availability]
- Package is already available in all Ubuntu versions.
- This is a backported version (Impish) to Bionic and Focal
** Summary changed:
- HWE kernels should enable BTF support to enable eBPF RO.CE support
+ HWE kernels should enable BTF support to enable eBPF CO-RE support
** Summary changed:
- HWE kernels should enable BTF support to enable eBPF CO-RE support
+ HWE kernels should support eBPF CO-RE
--
You
** No longer affects: dwarves-dfsg (Ubuntu Hirsute)
** No longer affects: linux (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926330
Title:
HWE kernels should enable BTF support
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-signed (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: grub2-signed (Ubuntu
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: dwarves-dfsg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926330
Title:
Public bug reported:
I had recent discussion with kernel team regarding support or not BTF in
HWE kernels (Bionic and Focal). Having CONFIG_DEBUG_INFO_BTF option
enabled for HWE kernels (v4.4 and v.4.8) would allow eBPF based code
(powered by libbpf or not) to be RO.CE
I'm pasting an email answer here so we keep track of all that has been
discussed for this issue:
> Me and Dan have been working recently on a customer case reported as
LP: #1915828. Turns out that some linker "magic" used inside libqb
broke pacemaker (and potentially any package using
removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
$ git-ubuntu tag --upload
$ git describe
upload/4.15.0-2ubuntu1.3
$ git push pkg upload/4.15.0-2ubuntu1.3
Counting objects: 11, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 2.07 KiB | 176.00 KiB/s, done.
Total 11 (delta
MP:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
** Description changed:
+ [Impact]
+
+ * The ss tool crashes when a query returns no results (seg fault)
+
+ [Test Case]
+
+
[rafaeldtinoco@iproute2issue iproute2]$ git unfixed
eb8559eff124221bfbafe934c4dbfe30f20604c0 is the first bad commit
commit eb8559eff124221bfbafe934c4dbfe30f20604c0
Author: Jean-Philippe Brucker
Date: Sat Mar 3 16:59:44 2018 +
ss: fix NULL dereference when rendering without header
It only affects Bionic:
[rafaeldtinoco@iproute2issue iproute2]$ git describe
eb8559eff124221bfbafe934c4dbfe30f20604c0
v4.15.0-103-geb8559ef
[rafaeldtinoco@iproute2issue ~]$ rmadison iproute2
iproute2 | 3.12.0-2 | trusty | source
iproute2 | 3.12.0-2ubuntu1.2
workaround:
sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1 | cat -
by not trying to control terminal WIDTH, segfault does not occur.
** Changed in: iproute2 (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a
Issues comes from:
(gdb) bt
#0 render (screen_width=144) at ss.c:1204
#1 main (argc=, argv=) at ss.c:4974
render (screen_width=144) at ss.c:1204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
mportance: Undecided
Status: Fix Released
** Affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: iproute2 (Ubuntu)
Status: New => Confirmed
** Also affects: iproute2 (Ubuntu Bionic)
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode
The keyboard is in Unicode (UTF-8) mode
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in Unicode (UTF-8) mode
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -s
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in
I have just faced this and kbd_mode -s also fixed the issue for me. The
behavior started out of nothing (something I did without perceiving most
likely). I'm using:
[rafaeldtinoco@fujitsu ~]$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:
Just a quick reminder.. we already made open-iscsi socket oriented and
that is also to be done with multipath-tools (I think I've done last 2
merges for both). I did not want to go for a full review on multipath-
tools this last cycle (but did for open-iscsi). FYIO.
The !container is because
Nice to read that! Thanks for the feedback.
** Changed in: nfs-utils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903974
Title:
issue reading netcdf4 files
** Attachment removed: "OpenPGP_0xA93E0E0AD83C0D0F.asc"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1903974/+attachment/5433792/+files/OpenPGP_0xA93E0E0AD83C0D0F.asc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
Isn't that happening because of differences in locking ?
https://rdrr.io/bioc/rhdf5/man/h5fileLocking.html
In NFSv4 file locking is part of the NFS protocol (different than NFSv3
that needed a network lock manager (NLM).
Perhaps you could follow instructions from RHDF5 and document here
For Focal...
I think we should SRU:
[rafaeldtinoco@groovy resource-agents]$ git log --oneline v4.5.0..HEAD --
heartbeat/azure-lb
d22700fc azure-lb: Don't redirect nc listener output to pidfile
that is the only fix I backported to Bionic (in the SRU being proposed)
and I think that it should
For Bionic, I think it's okay to have azure-lb backported as it is a
standalone shell script that will act as a resource agent. Unfortunately
I don't see AzEvents being backported and accepted as SRU just because
it takes some more changes for it to be integrated to existing Bionic
** Changed in: drbd-utils (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677843
Title:
Missing dep8 tests
To man
** Changed in: cluster-glue (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/166
Title:
Missing dep8 tests
To man
** Changed in: tgt (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863527
Title:
tgt man page points to non exist
** Changed in: libvirt (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: virt-manager (Ubuntu)
Assignee: Rafael David Tinoco (rafaeld
** Changed in: libvirt (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: virt-manager (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeld
** Changed in: pacemaker (Ubuntu Xenial)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848834
Title:
ClusterMon resource creat
** Changed in: resource-agents (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: fence-agents (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: rpcbind (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890276
Title:
rpcbind changes after bionic br
** Changed in: dlm (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866392
Title:
[bionic] dlm_controld won't st
** Changed in: procps (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls are ignored on b
** Changed in: ecryptfs-utils (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894899
Title:
smbd with "
** Changed in: lighttpd (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453463
Title:
undefined symbol: FAMNoExi
** Changed in: fence-agents (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: resource-agents (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: python-rtslib-fb (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865037
Title:
make the service f
** Changed in: qemu (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For BIONIC, azure-events also has to have:
commit cb87d027
azure-events: change message log level for the non action messages
Reduces the verbosity on the log when the RA has no events to process.
The messages can still be seen using the verbose parameter.
commit d2c47ec3
Fix
## To backport (or make sure it exists) to FOCAL:
# azure-lb
commit 771b49a1 (exists)
azure-lb: new resource agent
commit c5e465fc (exists)
azure-lb: remove reference to status from usage
commit d22700fc (needed)
azure-lb: Don't redirect nc listener output to pidfile
#
fence-agents (4.0.25-2ubuntu1.2) bionic; urgency=medium
* fence_aws backport from Focal (LP: #1894323):
+ d/p/lp1894323-01-fence_aws-new-agent.patch
-- Rafael David Tinoco Thu, 22 Oct 2020
04:47:00 +
[rafaeldtinoco@bionic fence-agents]$ git ubuntu tag --upload
** Description changed:
+ SRU reviewer: I got a complex backport for Focal thinking about
+ introducing a better version of fence_aws in Bionic but I abandoned the
+ idea and created a simple 1 patch fence_aws backport to Bionic (so it is
+ like Focal, and not both be like Groovy).
+
[Impact]
Thanks for all the attachments. This is Rafael from the Ubuntu Server
team. I have gone through all the logs and I could find the I/O errors
related to disk full (/var/log/syslog cannot be write) but that was a
long time ago and I'm assuming this is not the case here.
There are 2 (possible
** Description changed:
[Impact]
- * Currently Ubuntu Bionic does not have fence_aws available and that is
+ * Currently Ubuntu Bionic does not have fence_aws available and that is
needed in order to have a fully working HA solution in AWS environment.
- * fence_aws from Focal
To help with SRU review, I'm adding here the discussion taken from the
merge review.. basically I would like to give it a try backporting all
fixes for fence_aws into Focal and adding that same agent version in
Bionic (like a minor SRU exception). Instead of relying in the test case
results, I
** Description changed:
- This is a request to backport existing fence_aws agent into Bionic:
+ [Impact]
+
+ * Currently Ubuntu Bionic does not have fence_aws available and that is
+ needed in order to have a fully working HA solution in AWS environment.
+
+ * fence_aws from Focal
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-agents/+git/fence-agents/+merge/392432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894323
Title:
Everything is good and ready but I have discovered a small issue in the
Bionic Backport... and relates to:
https://access.redhat.com/solutions/4642491
The story is this: when declaring the fence_aws primitive, you can
either declare it as a single resource and describe the pcmk_host_map...
OR
Public bug reported:
After the SRU of LP: #1894323, it looks like a bad behavior in pacemaker
Bionic was exposed:
When declaring the fence_aws primitive, you can either declare it as a
single resource and describe the pcmk_host_map... OR you can declare one
fence resource PER NODE doing the
minor fix: "crm configure show" <- that would give us the cib in a human
readable way so we can reproduce with the same parameters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
(how to get fence_aws working with bionic and aws <- keywords for
google)
# Bionic fence_aws tests with the backport (from the ppa):
[rafaeldtinoco@bionic01 ~]$ crm status
Stack: corosync
Current DC: bionic01 (version 1.1.18-2b07d5c5a9) - partition with quorum
Last updated: Thu Oct 15 01:25:05
Moving on to Bionic backport now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894323
Title:
Add fence_aws fencing from v4.6.0 agent to Bionic
To manage notifications about this bug go to:
Using my proposed new version:
$ dpkg -l | grep -i fence
ii fence-agents 4.5.2-1ubuntu1~202010091535 amd64
Fence Agents for Red Hat Cluster
[rafaeldtinoco@focal01 ~]$ crm status
Cluster Summary:
* Stack: corosync
* Current DC: focal03 (version
(how to get fence_aws working with focal and aws <- keywords for google)
# Focal fence_aws tests without any backport (current version):
node 1: focal01
node 2: focal02
node 3: focal03
primitive fence-focal stonith:fence_aws \
params access_key= secret_key=""
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: fence-agents (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also providing a PPA containing a full v4.6.0 fence_aws backport to
Ubuntu Bionic fence-agents package at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1894323-bionic
with source at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-
I'm providing a PPA containing a full v4.6.0 fence_aws backport to
Ubuntu Focal fence-agents package at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1894323-focal
with source at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-
The autopkgtests results above look like a regression in crmsh DEP8
because of some other change (an apt-cache | grep "Package" command is
not working for crmsh) and unrelated to this upload (as other tests have
passed).
--
You received this bug notification because you are a member of Ubuntu
@jason,
I could verify this SRU but I'll let you handle it as you were the
reporter. Could you please change tags from "needed" to "done" when
you're good ? This will sinalize the update can migrate from -proposed
to -updates.
Thanks again for reporting this!
-rafaeldtinoco
--
You received
** Description changed:
[Impact]
* Cluster resource operation timeouts are not working correctly for
systemd resources and should be working. Timeouts are important in order
for the actions executed by pacemaker - for the systemd resource in
question - don't wait forever to start
** Changed in: pacemaker (Ubuntu Focal)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu Focal)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had to do a new MP for LP: #1881762 (a more minimal approach) and,
with that, I'll need to rebase this one (and probably re-think it based
on conversations for that SRU). Doing that...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[rafaeldtinoco@gitubuntu pacemaker]$ git push pkg --delete upload/2.0.3-3ubuntu4
To ssh://git.launchpad.net/ubuntu/+source/pacemaker
- [deleted] upload/2.0.3-3ubuntu4
[rafaeldtinoco@gitubuntu pacemaker]$ git tag -d upload/2.0.3-3ubuntu4
Deleted tag 'upload/2.0.3-3ubuntu4' (was
@racb could you, please, review it again for me ? I have done what we
agreed on.
Thanks a lot!
-rafaeldtinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not
After having my new fix (about to be uploaded):
[rafaeldtinoco@focal01 ~]$ crm status
Cluster Summary:
* Stack: corosync
* Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated: Sun Oct 4 14:19:09 2020
* Last change: Sun Oct 4 14:19:07 2020 by root via
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done by the resource)
- don't timeout before we're expecting (sometimes starting a resource can
- take more time than the default time
** Description changed:
- SRU reviewer:
-
- The merge request has been reviewed by @paelzer initially, before the
- SRU review. The most important comment is this:
-
-
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391398/comments/1030355
-
-
SRU reviewer:
https://pastebin.ubuntu.com/p/PcZq7Hr3NQ/
These are the functional tests results.
There was an issue running one test, I had to re-ran, and it is all
good:
Oct 01 04:09:09 Running test SimulStop (focal02) [ 1]
Oct 01 04:09:24 Stopping Cluster Manager on all
SRU reviewer:
https://pastebin.ubuntu.com/p/rgVVb66xGd/
These are the regression tests results. All good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not
I have just proposed a merge at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391596
but first I need the SRU on:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762
to be accepted, so I can move with this feature merge.
Will run
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: pacemaker (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896223
For the SRU reviewer:
I have uploaded the source code with the orig.tar.gz together (not sure
if this is a blocker as the package is waiting for approval in queue and
has not been rejected). Please find me on IRC so I can re-upload it if
needed.
Thank you!
** Description changed:
+ SRU
** Summary changed:
- [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers
+ no-quorum-policy=demote and on-fail=demote features for MSSQL servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
Do you have any updates on this ?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go
** Summary changed:
- [FFe] this is the no-quorum-policy feature (specially for mssql server)
+ [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done for the resource)
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the
** Also affects: pacemaker (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (
** Description changed:
+ [Impact]
+
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the actions (done for the resource)
+ don't timeout before we're expecting (sometimes starting a resource can
+ take more time than the default time
These are the patches being backported from upstream:
* Post 2.0.3 release fixes backported to Ubuntu: Fix resource timeout
functionality (LP: #1881762)
debian/patches/ubuntu-2.0.3-fixes/:
-
lp1881762-0001-e0e59163-Build-configure-remove-no-longer-needed-LIBADD_INTL-.patch
-
I'll provide a PPA with:
commit c9be5b271
Merge: 72a1f4834 08e3f7e44
Author: Ken Gaillot
Date: Fri Feb 21 14:57:57 2020
Merge pull request #1992 from kgaillot/times
Fix systemd support when using clock_gettime()
and
commit 8254f3d25
Merge: 0625eb1a2 71ae72df9
Author: Ken
I'm on it now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
This bug was serving me as a base to track tested fencing agents in
Bionic, Focal and Groovy. No more reason to keep it opened, closing it
as invalid.
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: fence-agents (Ubuntu Eoan)
Status: Won't
Ubuntu HA wise:
I'm recommending all HA clusters to have the cluster interfaces
configured with systemd-networkd DIRECTLY instead of wrapping it through
netplan.io. At least until we're sure that HA has no issues with
netplan.io, having it configured directly will allow us to isolate
possible
All good with published package. Good to go.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: multipath-tools (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202
Title:
Multipathd hangs with l
** Changed in: open-iscsi (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892292
Title:
iscsi boot fails to b
** Summary changed:
- [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
+ [FFe] this is the no-quorum-policy feature (specially for mssql server)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ ./CTSlab.py --nodes "groovy01 groovy02 groovy03" --once --no-loop-tests
--no-unsafe-tests --outputfile ~/cts.log
Sep 24 04:40:29 BEGINNING 15 TESTS
Sep 24 04:40:29 Stack: corosync 2+ (crm-corosync)
Sep 24 04:40:29 Schema: pacemaker-3.0
Sep 24
Summary
* Passed: iso8601- Invalid period - []
* Passed: iso8601- Invalid period - [2019-01-01 00:00:00Z]
* Passed: iso8601- Invalid period - [2019-01-01 00:00:00Z/]
* Passed: iso8601- Invalid period - [PT2S/P1M]
* Passed: iso8601- Invalid period -
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391162
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896223
Title:
[FFe]
that should also be checked for backport
(backporting fence_ec2 to Focal and Bionic if possible).
I opened the following bug for this:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1896696
** Changed in: fence-agents (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco
Public bug reported:
In Bug:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1895355
I have backported fixes and a new feature to cluster-glue:
# ec2 stonith agent support and fixes
7c84a6ae Fix EC2 stonith plugin
27e83692 Fix: stonith:ibmhmc: Add "managedsyspat" and "password" as
1 - 100 of 3504 matches
Mail list logo
