[Bug 1274320] Re: Error: diskfilter writes are not supported
** 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 Bionic) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: grub2 (Ubuntu Focal) Status: New => Confirmed ** Changed in: grub2-signed (Ubuntu Bionic) Status: New => Confirmed ** Changed in: grub2-signed (Ubuntu Focal) 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/1274320 Title: Error: diskfilter writes are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926330] Re: HWE kernels should enable BTF support to enable eBPF RO.CE support
** 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: HWE kernels should enable BTF support to enable eBPF RO.CE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926330] [NEW] HWE kernels should enable BTF support to enable eBPF RO.CE support
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 (https://github.com/rafaeldtinoco/portablebpf for more information). By allowing runtime relocations, using provided BTF, libbpf binaries might end up running, without modifications, in different kernel versions (from Bionic HWE v5.4 kernel to Hirsute v5.11). A good example would be to support tools such as: https://github.com/aquasecurity/tracee/discussions/713#discussioncomment-665641 An ebpf powered backend for a containers security solution. Considering: $ rmadisonb dwarves dwarves | 1.9-1 | precise/universe | amd64 dwarves | 1.10-2 | trusty | amd64 dwarves | 1.10-2.1 | xenial/universe | amd64 dwarves | 1.10-2.1build1 | bionic/universe | amd64 dwarves | 1.15-2 | focal/universe | amd64 dwarves | 1.17-1 | groovy/universe | amd64 dwarves | 1.20-1 | hirsute/universe | amd64 dwarves | 1.20-1 | impish/universe | amd64 And the fact that the 'pahole' binary, from dwarves package, is the one to blame, not to have CONFIG_DEBUG_INFO_BTF available, for this bug to be solved we would have to provide a backport of dwarves (at least 1.17-1) to Bionic and Focal. It could have another name (not to mess with original dwarves package and its dependencies) and it is unclear if it needs to be in [main] or [universe]. Question: Would have dwarves backported in -backports be enough for Bionic and Focal HWE kernels compilation to have CONFIG_DEBUG_INFO_BTF enabled ? ** Affects: dwarves-dfsg (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: dwarves-dfsg (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: dwarves-dfsg (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: dwarves-dfsg (Ubuntu Groovy) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Summary changed: - HWE kernels should enable BTF support to enable new eBPF based code + HWE kernels should enable BTF support to enable eBPF RO.CE support ** Also affects: dwarves-dfsg (Ubuntu) Importance: Undecided Status: New ** Changed in: dwarves-dfsg (Ubuntu Groovy) Status: New => Fix Released ** Changed in: dwarves-dfsg (Ubuntu Focal) Status: New => Confirmed ** Changed in: dwarves-dfsg (Ubuntu Bionic) 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: HWE kernels should enable BTF support to enable eBPF RO.CE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1926330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915828] Re: pacemaker fails to release clustered filesystem dlm locks on failover
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 QB_LOG_INIT_DATA from
the library or even every packaged linked against libqb).
I have checked libqb commits and: https://paste.ubuntu.com/p/vTdYJdC4Hc/
. I see that upstream added some options in configure.ac related to the
linking issue, even quoting debian/ubuntu option to override libtool
variable by force. There is also an existing test for the
__attribute__((section("__verbose"))) breakage detection now
(gcc_has_attribute_section_visible variable in configure.ac.
> Dan found an ABI-compatible way of mitigating the problem by
rebuilding pacemaker with the QB_KILL_ATTRIBUTE_SECTION defined. This
strips the magic and makes pacemaker useful again.
I see the mitigation (QB_KILL_ATTRIBUTE_SECTION) comes from:
--
32555d8 tests: add a script to generate callsite-heavy logging client…
...so as to evaluate use of resources. In particular, the intention
here is to uncover the observable differences between the same logging
code built with callsite section (default when available) and
purposefully (overriding that default by force) without it.
...
--
And they even added “tests/functional/log_callsite_bench_gen.py” to
measure the impact of this mitigation.
I’m particularly worried with:
—
Based on the above, we can conclude that leveraging the callsite
section for logging as facilitated by the toolchain intrinsics is
beneficial, especially for performance-critical applications (corosync
being the showcase here). Therefore it's desired to struggle for
retaining this nifty trick despite some troubles emerged with recent
binutils releases (starting with 2.29) and the changed behaviour we
relied on so far in respective ld.bfd linkers (as mentioned in
preceding commits). That motive is immediately followed -- well,
judging the impact fairly, actually outclassed -- with the intention
to preserve binary compatibility (incl. continuous library support for
callsite section offloading spread in the existing client space widely
for quite some years already) to the utmost extent possible.
--
I believe this will be accepted by the SRU team but this, for sure, has
to be mentioned in the public bug. I would add to [regression potential]
the fact that the logging mechanism would stir heap more often (commit
log has even a time execution delta).
Shouldn’t this bug also affect all the libqb0 rdepends ? I can see
pacemaker, sbd, corosync and usbguard source packages.
> The problem is (more details in comments #3-#5) some symbols disappear
from the package. Those symbols doesn't seem to be used anywhere
explicitly, but we were wondering if it's ok to just drop those symbols
or maybe to implement a change in libqb to create dummy constructors
(e.g. https://pastebin.canonical.com/p/Y4fk747YfK/) to ensure the
symbols are available just in case.
For the pacemaker fix I’ll let the SRU team to discuss whether they
would like to have symbols (or not) the symbols in the new binary (after
this fix). I don’t think those symbols are used elsewhere (from rdepends
of libcrm* they would only be used by either pacemaker OR sbd).
I think next step here is to offer a patch and ask for the SRU team
input/review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915828
Title:
pacemaker fails to release clustered filesystem dlm locks on failover
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1915828/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
# verfication $ dpkg -l iproute2 | grep ii ii iproute2 4.15.0-2ubuntu1.3 amd64networking and traffic control tools $ ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 && echo worked worked good to migrate. thank you. -rafaeldtinoco ** Tags 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
$ 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 7), reused 0 (delta 0) To ssh://git.launchpad.net/ubuntu/+source/iproute2 * [new tag] upload/4.15.0-2ubuntu1.3 -> upload/4.15.0-2ubuntu1.3 $ debdiff *.dsc | diffstat changelog | 7 +++ patches/lp1913187-ss-fix-NULL-dereference-when-rendering.patch | 40 patches/series | 1 + 3 files changed, 48 insertions(+) [rafaeldtinoco@iproute2issue ubuntu]$ dput ubuntu ./iproute2_4.15.0-2ubuntu1.3_source.changes Checking signature on .changes gpg: ./iproute2_4.15.0-2ubuntu1.3_source.changes: Valid signature from A93E0E0AD83C0D0F Checking signature on .dsc gpg: ./iproute2_4.15.0-2ubuntu1.3.dsc: Valid signature from A93E0E0AD83C0D0F Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading iproute2_4.15.0-2ubuntu1.3.dsc: done. Uploading iproute2_4.15.0-2ubuntu1.3.debian.tar.xz: done. Uploading iproute2_4.15.0-2ubuntu1.3_source.buildinfo: done. Uploading iproute2_4.15.0-2ubuntu1.3_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
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]
+
+ * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
+ Segmentation fault
+
+ [Where problems could occur]
+
+ * The ss tool is impacted and it has its code changed for the fix.
+
+ * The fix is a clean cherry-pick and straightforward (moving
+ declaration after a NULL check).
+
+ [Other Info]
+
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
** Description changed:
[Impact]
- * The ss tool crashes when a query returns no results (seg fault)
+ * The ss tool crashes when a query returns no results (seg fault)
[Test Case]
- * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
- Segmentation fault
+ * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
+ Segmentation fault
+
+ * PPA with the fix:
+ https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
- * The ss tool is impacted and it has its code changed for the fix.
+ * The ss tool is impacted and it has its code changed for the fix.
- * The fix is a clean cherry-pick and straightforward (moving
+ * The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
-
+
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
[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 When ss is invoked with the no-header flag, if the query doesn't return any result, render() is called with 'buffer' uninitialized. This currently leads to a segfault. Ensure that buffer is initialized before rendering. The bug can be triggered with: ss -H sport = 10 Signed-off-by: Jean-Philippe Brucker Acked-by: Stefano Brivio Signed-off-by: Stephen Hemminger :04 04 bf8f626f1c0b85bd690dab60d4f74db292ac8e65 6174ebf0728edab46c62b713f6aee495eef81cb5 M misc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
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 | trusty-updates | source iproute2 | 4.3.0-1ubuntu3| xenial | source iproute2 | 4.3.0-1ubuntu3.16.04.5| xenial-updates | source iproute2 | 4.15.0-2ubuntu1 | bionic | source iproute2 | 4.15.0-2ubuntu1.1 | bionic-security | source iproute2 | 4.15.0-2ubuntu1.2 | bionic-updates | source iproute2 | 4.18.0-1ubuntu2~ubuntu18.04.1 | bionic-backports | source iproute2 | 5.5.0-1ubuntu1| focal| source iproute2 | 5.7.0-1ubuntu1| groovy | source iproute2 | 5.9.0-1ubuntu1| hirsute | source iproute2 | 5.10.0-2ubuntu1 | hirsute-proposed | source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] Re: iproute2 segfaults when filtering sockets
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. https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913187] [NEW] iproute2 segfaults when filtering sockets
Public bug reported:
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
** Affects: iproute2 (Ubuntu)
Importance: 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)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: iproute2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
[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 raw (scancode) mode and it was "fixed". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
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:20.10 Codename: groovy apt-history shows last apt command was yesterday (for my host) and it was working fine yesterday. Unfortunately I have no time to dig into this now, but wanted to state that this still happens in 20.10 (and possibly 20.04 according to @ribalkin report). ** Also affects: kbd (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: kbd (Ubuntu Maverick) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Maverick) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Maverick) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904920] Re: multipathd gets started by default on VM instances
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 multipath tools talk with systemd-udev and that is only supported in the host (just like iscsid does). That is why there might be a condition not to start on container systems, just because the container might not be able to control udev/dm within kernel (but, again, that was for me to do this cycle... will have to do next one, after my current assignment, or someone else can do it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904920 Title: multipathd gets started by default on VM instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1904920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903974] Re: issue reading netcdf4 files with nfs v3 on ubuntu 20.04
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 with nfs v3 on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1903974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903974] Re: issue reading netcdf4 files with nfs v3 on ubuntu 20.04
** 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. https://bugs.launchpad.net/bugs/1903974 Title: issue reading netcdf4 files with nfs v3 on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1903974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1903974] [NEW] issue reading netcdf4 files with nfs v3 on ubuntu 20.04
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 your discoveries ? Thanks ** Attachment added: "OpenPGP_0xA93E0E0AD83C0D0F.asc" https://bugs.launchpad.net/bugs/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. https://bugs.launchpad.net/bugs/1903974 Title: issue reading netcdf4 files with nfs v3 on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1903974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895343] Re: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic
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 also be SRU'ed to Focal as the fix is straightforward. In regards to azure-events: >From Focal to HEAD upstream we have: [rafaeldtinoco@groovy resource-agents]$ git log --oneline v4.5.0..HEAD -- heartbeat/azure-events* 1ab5d71b azure-events: report error if jsondata not received f2bf1d8a azure-events: import URLError and encode postData when necessary 57424bd1 azure-events: only decode() when exec() output not of type str cc69a8fa azure-events: handle exceptions in urlopen (#1496) but.. from Focal to Groovy we have only: cc69a8fa azure-events: handle exceptions in urlopen (#1496) I think there won't be anything to be done unless we have a real problem we can have a test case for (and solve in another SRU). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895343] Re: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic
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 resource-agents. These are the patches implementing the AzEvents (renamed to azure-events later): 328bb0e 2018-07-18 10:11 -0700 TNiekamp AzEvents: Use configure to replace shebang line 416f0b1 2018-09-14 15:21 -0700 TNiekamp Implemented review feedback from krig e7b1a18 2018-10-17 09:10 +0200 KGrönlund dev: AzEvents: Use pacemaker commands to set standby 9890deb 2018-10-17 09:06 +0200 KGrönlund dev: AzEvents: Start using ocf.py ca15b9d 2018-10-18 09:23 +0200 KGrönlund dev: azure-events: Add custom user agent and it would require the ocf.py to be brought as well, and then all the compilation changes regarding auto tools to recognize python scripts... not suitable for a SRU, for sure. With that said, I'll keep my merge request to bring *at least* the azure-lb resource agent to Bionic at: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/resource- agents/+git/resource-agents/+merge/392746 My suggestion to those who need azure-events is to either migrate to Focal or Groovy, or to use the back-ported Groovy HA stack at: https://launchpad.net/~ubuntu-ha/+archive/ubuntu/groovy-ha-stack ** Changed in: resource-agents (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677843] Re: Missing dep8 tests
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1677843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677776] Re: Missing dep8 tests
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863527] Re: tgt man page points to non existent example config file
** 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 existent example config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1863527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832395] Re: "kvm_init_vcpu failed: Invalid argument" error on ARM big.LITTLE boards
** 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 (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/1832395 Title: "kvm_init_vcpu failed: Invalid argument" error on ARM big.LITTLE boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832394] Re: qemu-system-aarch64 error: MSI-X is not supported by interrupt controller
** 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 (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/1832394 Title: qemu-system-aarch64 error: MSI-X is not supported by interrupt controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848834] Re: ClusterMon resource creation core-dumps while created with extra_option -E
** 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 creation core-dumps while created with extra_option -E To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1848834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869643] Re: {fence, resource}-agents: PATH for all binaries called by all agents should be resolvable
** 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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869643
Title:
{fence,resource}-agents: PATH for all binaries called by all agents
should be resolvable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1869643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890276] Re: rpcbind changes after bionic broke rup broadcast feature
** 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 broke rup broadcast feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1890276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866392] Re: [bionic] dlm_controld won't start due to missing device files
** 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 start due to missing device files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1866392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctls are ignored on boot
** 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 boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894899] Re: smbd with "obey pam restrictions" enabled unmounts my interactive users' ecryptfs home directory
** 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 "obey pam restrictions" enabled unmounts my interactive users' ecryptfs home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1894899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453463] Re: undefined symbol: FAMNoExists
** 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: FAMNoExists To manage notifications about this bug go to: https://bugs.launchpad.net/lighttpd/+bug/1453463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863677] Re: {fence-resource}-agents: split supported/unsupported fence agents AND adjust depends/recommends
** 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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863677
Title:
{fence-resource}-agents: split supported/unsupported fence agents AND
adjust depends/recommends
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1863677/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
** 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 fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/rtslib-fb/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841066] Re: ARCH_CAPABILITIES guest capability detection
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841066 Title: ARCH_CAPABILITIES guest capability detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1841066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895343] Re: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic
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 implicit bytes conversion that breaks py3. Reduces the amount of errors messages using default value on crm_attribute commit ca15b9dc dev: azure-events: Add custom user agent commit 9890deba dev: AzEvents: Start using ocf.py (#1161) commit e7b1a18a dev: AzEvents: Use pacemaker commands to set standby commit 416f0b1f Implemented review feedback from krig So it can be in the same level as Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895343] Re: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic
## 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 # azure-events (to the same code level as in Focal) commit 2512b396 (v4.2.0) (exists) Initial version of the AzEvents RA commit 328bb0e4 (exists) AzEvents: Use configure to replace shebang line https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap /high-availability-guide-suse-nfs (Shows de issue about netcat fix for azure-lb) ## To backport (or make sure it exists) to BIONIC: ## azure-lb commit 771b49a1 (needed) azure-lb: new resource agent commit c5e465fc (needed) azure-lb: remove reference to status from usage commit d22700fc (needed) azure-lb: Don't redirect nc listener output to pidfile ## azure-events (to the same code level as in Focal) commit 2512b396 (v4.2.0) (needed) Initial version of the AzEvents RA commit 328bb0e4 (needed) AzEvents: Use configure to replace shebang line -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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 [rafaeldtinoco@bionic fence-agents]$ git describe upload/4.0.25-2ubuntu1.2 [rafaeldtinoco@bionic fence-agents]$ git push pkg upload/4.0.25-2ubuntu1.2 Counting objects: 15, done. Delta compression using up to 24 threads. Compressing objects: 100% (15/15), done. Writing objects: 100% (15/15), 4.49 KiB | 460.00 KiB/s, done. Total 15 (delta 10), reused 0 (delta 0) To ssh://git.launchpad.net/ubuntu/+source/fence-agents * [new tag] upload/4.0.25-2ubuntu1.2 -> upload/4.0.25-2ubuntu1.2 [rafaeldtinoco@bionic ubuntu]$ debdiff fence-agents_4.0.25-2ubuntu1.1.dsc fence-agents_4.0.25-2ubuntu1.2.dsc | diffstat changelog |7 + control|5 - patches/lp1894323-01-fence_aws-new-agent.patch | 286 + patches/series |1 4 files changed, 298 insertions(+), 1 deletion(-) [rafaeldtinoco@bionic ubuntu]$ dput ubuntu fence-agents_4.0.25-2ubuntu1.2_source.changes Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading fence-agents_4.0.25-2ubuntu1.2.dsc: done. Uploading fence-agents_4.0.25-2ubuntu1.2.debian.tar.xz: done. Uploading fence-agents_4.0.25-2ubuntu1.2_source.buildinfo: done. Uploading fence-agents_4.0.25-2ubuntu1.2_source.changes: done. Successfully uploaded packages. Note: the fence_aws agent primitive should be declared as: primitive fence-bionic stonith:fence_aws \ params access_key= secret_key="" region=us-east-1 pcmk_host_map="bionic01:i-068e134de1beddc7f;bionic02:i-0136eddd045ceb7e2;bionic03:i-0de279ab4e6d642c8" and cluster properties as: have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=bionic crm configure might complain about you not specifying the "plug" argument, you can safely ignore that as this fence_agent does not require the plug argument (and this pacemaker version has an issue when plug is given, see comment #11 for more information). ** Changed in: fence-agents (Ubuntu Focal) Status: In Progress => Won't Fix -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
** 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] * 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 fence-agents (4.5.2-1) is missing some fixes that happened in between Focal and Groovy versions. With that, I initially opted to fully bring all the fixes from version 4.6.0 to Focal and backport this same version to Bionic (this way Bionic and Focal were in the same level). * After MR reviews, thinking about the SRU review, I agreed to minimize this change making Ubuntu Bionic fence_aws agent just like focal and working in any needed Focal fix for fence_aws (as long as there was a test case for it). [Test Case] * Provision 3 nodes in AWS with Ubuntu Focal (and Ubuntu Bionic) and configure it adding the following primitive as a fencing resource: primitive fence-focal stonith:fence_aws params access_key="" secret_key="" region="us-east-1" pcmk_host_map="focal01:i-034dc89cca4310b03;focal02:i-0a160b14b40f1330a;focal03:i-03b6976ab0a7f377c" and the cluster cib options: property cib-bootstrap-options: \ have-watchdog=false \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=bionic * After that you can remove the interconnect of one of the nodes and watch the cluster to shutdown the node that was disconnected from the cluster ring. [Regression Potential] * Bionic wise: - Same as focal, but here it is even better situation as there isn't an existing fence_aws agent. Biggest problem here could be introduce something that does not fully work (which is technically not a regression). [Other Info] This is a request from AWS to backport existing fence_aws agent into Bionic - Currently fence-agents Ubuntu Bionic version is at: 4.0.25-2ubuntu1 and the fence_aws new agent started at: $ git tag --contains a3f45322 | head -1 v4.1.0 -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
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 unrelated) issues I could see: 1) lots of CDB inquiry SCSI errors: sd 2:0:0:4: [sdj] tag#76 CDB: Inquiry 12 01 c9 00 fe 00 sd 2:0:0:4: [sdj] tag#76 Sense Key : Illegal Request [current] sd 2:0:0:4: [sdj] tag#76 Add. Sense: Invalid field in cdb sd 2:0:0:5: [sdl] tag#65 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 2:0:0:5: [sdl] tag#65 CDB: Inquiry 12 01 c9 00 fe 00 sd 2:0:0:5: [sdl] tag#65 Sense Key : Illegal Request [current] sd 2:0:0:5: [sdl] tag#65 Add. Sense: Invalid field in cdb sd 3:0:0:1: [sdr] tag#108 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:1: [sdr] tag#108 CDB: Inquiry 12 01 c9 00 fe 00 sd 3:0:0:1: [sdr] tag#108 Sense Key : Illegal Request [current] sd 3:0:0:1: [sdr] tag#108 Add. Sense: Invalid field in cdb sd 3:0:0:2: [sdt] tag#96 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:2: [sdt] tag#96 CDB: Inquiry 12 01 c9 00 fe 00 sd 3:0:0:2: [sdt] tag#96 Sense Key : Illegal Request [current] sd 3:0:0:2: [sdt] tag#96 Add. Sense: Invalid field in cdb sd 3:0:0:3: [sdu] tag#103 Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK sd 3:0:0:3: [sdu] tag#103 CDB: Inquiry 12 01 c9 00 fe 00 likely because storage server is not accepting those inquiries on non existent LUNs (were they removed from the system ? The storage server admin can tell you why your INQ CDB was denied.. but, since this is an INQ command AND there are no further I/O errors, I think it is safe to consider this as non-fatal and unrelated to this bug as well. 2) I have tried to reproduce the issue locally but was not able to. I'm sorry for the back and forth, if we could reproduce it here it would way faster. With that said, it is unclear to me if have you tried editing "/usr/lib/rsyslog/rsyslog-rotate" and changing: systemctl kill -s HUP rsyslog.service for systemctl restart rsyslog.service to see if this mitigates the issue ? That will help isolate the problem and allow us to know if the problem is related to the HUP signal handling feature in rsyslog (which is responsible for cleaning up opened file descriptors and might be causing this in some situation). By always restarting the service we will do a full initialization of descriptors and could be a good indicator if that is the problem. That is the suggestion right now because from all the log files, the only messages coming out of rsyslog were related to the HUP signal handler. This may also be a "hotfix" if it works, because there are some fixes in between the rsyslog you're using and the latest, one of them being: commit 723f6fdfa Author: John Brooks Date: Wed Jul 3 15:10:30 2019 rsyslogd: Fix race between signals and main loop timeout The main loop sleeps in a select() call for a long interval in order to periodically run housekeeping tasks. The main loop is also responsible for responding to flags set by signal handlers, so this sleeping should be interrupted by signals so that it can check those flags. However, a signal could be delivered between when the flags are checked and when select() is called. In which case the main loop will block for the full interval (currently 10 minutes) before handling the signal. If this occurs, it could take up to 10 minutes for rsyslogd to terminate after a SIGTERM or respond to SIGHUP. Fix this by blocking signals before checking the flags and using pselect() to unblock the signals while waiting. This is recommended by the select(2) manual page to avoid this very issue. Signed-off-by: John Brooks among others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
** 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 fence-agents (4.5.2-1) is missing some important - fixes that happened in between Focal and Groovy versions. With that, I - opted to fully bring all the fixes from version 4.6.0 to Focal and - backport this same version to Bionic (this way Bionic and Focal are in - the same level also). + * fence_aws from Focal fence-agents (4.5.2-1) is missing some fixes + that happened in between Focal and Groovy versions. With that, I + initially opted to fully bring all the fixes from version 4.6.0 to Focal + and backport this same version to Bionic (this way Bionic and Focal were + in the same level). + + * After MR reviews, thinking about the SRU review, I agreed to minimize + this change making Ubuntu Bionic fence_aws agent just like focal and + working in any needed Focal fix for fence_aws (as long as there was a + test case for it). [Test Case] - * Provision 3 nodes in AWS with Ubuntu Focal (and Ubuntu Bionic) and + * Provision 3 nodes in AWS with Ubuntu Focal (and Ubuntu Bionic) and configure it adding the following primitive as a fencing resource: primitive fence-focal stonith:fence_aws params access_key="" secret_key="" region="us-east-1" pcmk_host_map="focal01:i-034dc89cca4310b03;focal02:i-0a160b14b40f1330a;focal03:i-03b6976ab0a7f377c" and the cluster cib options: property cib-bootstrap-options: \ - have-watchdog=false \ - cluster-infrastructure=corosync \ - stonith-enabled=on \ - stonith-action=reboot \ - no-quorum-policy=stop \ - cluster-name=bionic + have-watchdog=false \ + cluster-infrastructure=corosync \ + stonith-enabled=on \ + stonith-action=reboot \ + no-quorum-policy=stop \ + cluster-name=bionic - * After that you can remove the interconnect of one of the nodes and + * After that you can remove the interconnect of one of the nodes and watch the cluster to shutdown the node that was disconnected from the cluster ring. [Regression Potential] - * Focal wise: + * Bionic wise: -- We're only touching agents/aws/fence_aws.py and - tests/data/metadata/fence_aws.xml files. This reduces *a lot* the scope - of the code change and helps in the SRU approval (as the change is - confined into the aws fence agent only). - -- Biggest problem here could be related to rebuilds, as the fence- - agents are directly called from pacemaker as "exec'ed scripts with right - arguments", and there is no change to any part of the fence-agents core - package. - - * Bionic wise: - -- Same as focal, but here it is even better situation as there isn't + - Same as focal, but here it is even better situation as there isn't an existing fence_aws agent. Biggest problem here could be introduce something that does not fully work (which is technically not a regression). [Other Info] - This is a request from AWS to backport existing fence_aws agent into - Bionic: - - - commit 50772024 - Author: Oyvind Albrigtsen - Date: Mon May 25 12:07:14 2020 - - fence_aws: improve boto3_debug boolean handling - - commit be206158 - Author: Oyvind Albrigtsen - Date: Mon May 25 12:03:53 2020 - - fence_aws: catch ConnectionError and suppress traceback for caught - exceptions - - commit 9758f8c8 - Author: Oyvind Albrigtsen - Date: Tue Mar 24 14:31:13 2020 - - fence_aws: fix Python 3 encoding issue - - commit 3f5676a7 - Author: gguifelixamz <45173771+gguifelix...@users.noreply.github.com> - Date: Fri Mar 20 14:41:07 2020 - - fence_aws: Fix fence race, logging improvement and new debug option - (#323) - - * fence_aws: Fix fence race condition by checking local instance status - * fence_aws: Use local logger and improve logging experience - * fence_aws: Decouple boto3 and botocore debug logging from local logging - - commit 1c2f791b - Author: Oyvind Albrigtsen + This is a request from AWS to backport existing fence_aws agent into Bionic: + @redhat.com> Date: Thu Mar 5 13:10:29 2020 fence_aws: improve connect parameter logic, so region can be specified as parameter, while using role or keys from ~/.aws/config commit 7ac16fb2 Author: Oyvind Albrigtsen Date: Fri Jan 31 14:53:47 2020 fence_aws: improve logging and metadata/usage text commit a3f45322 Author: Oyvind Albrigtsen Date: Tue Mar 7 10:04:49 2017 fence_aws: new agent Currently fence-agents Ubuntu Bionic version is at: 4.0.25-2ubuntu1 and the fence_aws new agent started at: $ git tag --contains a3f45322 | head -1 v4.1.0 ** Description changed: [Impact] * Currently Ubuntu Bionic does not have fence_aws available and that is
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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 would like to rely in my functional/regression tests for a pacemaker cluster configured in AWS with this new agent (if possible). Discussion with @bryce from the Ubuntu Server Team: > I also read through each of the patches to understand what they do, and make sure the changes look safe, which they indeed do. One thought I had though is that the common theme in the patches is improvements to debug/logging output; the SRU team sometimes demurs over debug/logging changes as less important than actual bug fixes. At least you'll want to include good justification on this in the SRU text. My justification to that is that Bionic does not have anything and I really would like Focal to be "as good as Focal", instead of adding something better in Bionic just because it did not have anything. Or even adding something not as good as Groovy just because of formal reasons. > Commit 1c2f791b changes the cli option behavior, which is akin to an API change. I.e. before if you passed --region but not --access-key or --secret-key it would ignore --region and use configured values, with this change you can specify just --region and the keys will come from the config file. This feels more like a behavioral change than a bug fix, so I might anticipate some pushback from the SRU team on this. Yes, this was per AWS request... and follows the same idea as the previous justification. This change allows one not to explicitly put the access or secret keys in the cluster CIB file (so its more secure also). > In terms of SRU, I notice there are not (upstream|downstream) bug reports associated with the patches, which may make one wonder if these fix actual defects encountered in the wild, or are more like clarification/refactoring. > I understand the logic of since the scripts don't exist in bionic to bring the current versions rather so as to have the most up to date code. But as you mention this then leaves a weird situation and having to pull delta into focal that otherwise might not be needed. > Did you consider pulling the fence_aws from focal rather than the one in groovy? (And then cherrypicking the most relevant bug fixes from groovy, like the encoding fix and/or the race fix?) Yes I did.. unfortunately its a SRU philosophical question. I'm considering fence_aws here as a confined code that is mostly supported by AWS themselves. I can go on that direction but I feel it is not the best for our user base. > Alternatively, if you definitely do want to backport the whole stack, did you consider filing for an SRU exception for this package? If it really is important to keep the scripts identical on all LTS's that might be a better long term approach. That would be a no-go because of agents metadata and pacemaker. Pacemaker should be able to handler older and newer fence-agents packages.. but it is not as good as "compatible with all further versions". I would like this to be considered a small SRU exception as it is for fence_aws only. -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
** 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 fence-agents (4.5.2-1) is missing some important + fixes that happened in between Focal and Groovy versions. With that, I + opted to fully bring all the fixes from version 4.6.0 to Focal and + backport this same version to Bionic (this way Bionic and Focal are in + the same level also). + + [Test Case] + + * Provision 3 nodes in AWS with Ubuntu Focal (and Ubuntu Bionic) and + configure it adding the following primitive as a fencing resource: + + primitive fence-focal stonith:fence_aws params access_key="" secret_key="" + region="us-east-1" pcmk_host_map="focal01:i-034dc89cca4310b03;focal02:i-0a160b14b40f1330a;focal03:i-03b6976ab0a7f377c" + + and the cluster cib options: + + property cib-bootstrap-options: \ + have-watchdog=false \ + cluster-infrastructure=corosync \ + stonith-enabled=on \ + stonith-action=reboot \ + no-quorum-policy=stop \ + cluster-name=bionic + + * After that you can remove the interconnect of one of the nodes and + watch the cluster to shutdown the node that was disconnected from the + cluster ring. + + [Regression Potential] + + * Focal wise: + +- We're only touching agents/aws/fence_aws.py and + tests/data/metadata/fence_aws.xml files. This reduces *a lot* the scope + of the code change and helps in the SRU approval (as the change is + confined into the aws fence agent only). + +- Biggest problem here could be related to rebuilds, as the fence- + agents are directly called from pacemaker as "exec'ed scripts with right + arguments", and there is no change to any part of the fence-agents core + package. + + * Bionic wise: + +- Same as focal, but here it is even better situation as there isn't + an existing fence_aws agent. Biggest problem here could be introduce + something that does not fully work (which is technically not a + regression). + + [Other Info] + + This is a request from AWS to backport existing fence_aws agent into + Bionic: commit 50772024 Author: Oyvind Albrigtsen Date: Mon May 25 12:07:14 2020 - fence_aws: improve boto3_debug boolean handling + fence_aws: improve boto3_debug boolean handling commit be206158 Author: Oyvind Albrigtsen Date: Mon May 25 12:03:53 2020 - fence_aws: catch ConnectionError and suppress traceback for caught + fence_aws: catch ConnectionError and suppress traceback for caught exceptions commit 9758f8c8 Author: Oyvind Albrigtsen Date: Tue Mar 24 14:31:13 2020 - fence_aws: fix Python 3 encoding issue + fence_aws: fix Python 3 encoding issue commit 3f5676a7 Author: gguifelixamz <45173771+gguifelix...@users.noreply.github.com> Date: Fri Mar 20 14:41:07 2020 - fence_aws: Fix fence race, logging improvement and new debug option (#323) - - * fence_aws: Fix fence race condition by checking local instance status - * fence_aws: Use local logger and improve logging experience - * fence_aws: Decouple boto3 and botocore debug logging from local logging + fence_aws: Fix fence race, logging improvement and new debug option + (#323) + + * fence_aws: Fix fence race condition by checking local instance status + * fence_aws: Use local logger and improve logging experience + * fence_aws: Decouple boto3 and botocore debug logging from local logging commit 1c2f791b Author: Oyvind Albrigtsen Date: Thu Mar 5 13:10:29 2020 - fence_aws: improve connect parameter logic, so region can be specified - as parameter, while using role or keys from ~/.aws/config + fence_aws: improve connect parameter logic, so region can be specified + as parameter, while using role or keys from ~/.aws/config commit 7ac16fb2 Author: Oyvind Albrigtsen Date: Fri Jan 31 14:53:47 2020 - fence_aws: improve logging and metadata/usage text + fence_aws: improve logging and metadata/usage text commit a3f45322 Author: Oyvind Albrigtsen Date: Tue Mar 7 10:04:49 2017 - fence_aws: new agent + fence_aws: new agent Currently fence-agents Ubuntu Bionic version is at: 4.0.25-2ubuntu1 and the fence_aws new agent started at: $ git tag --contains a3f45322 | head -1 v4.1.0 -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
** 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: Add fence_aws fencing from v4.6.0 agent to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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 you can declare one fence resource PER NODE doing the exact same thing BUT using the "plug/port" resource argument. The thing is... in Focal, both methods work but in Bionic, the second method does not work. It is not a big deal as there are some fence agents designed to work with "pcmk_host_map" only, and some others are designed to work with "plug/port" argument... but I have opened the bug: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1900374 to deal with this in a later moment (might require pacemaker bisecting, etc) For this SRU.. after it is complete, the correct way of declaring the fence_aws resource is: # focal node 1: focal01 node 2: focal02 node 3: focal03 primitive fence-focal stonith:fence_aws \ params access_key= secret_key="" region=us-east-1 pcmk_host_map="focal01:i-abcdefgh;focal02:i-ijlmnop;focal03:i-qrstuvxz" property cib-bootstrap-options: \ have-watchdog=false \ dc-version=2.0.3-4b1f869f0f \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=focal # bionic node 1: bionic01 node 2: bionic02 node 3: bionic03 primitive fence-bionic stonith:fence_aws \ params access_key= secret_key="" region=us-east-1 pcmk_host_map="bionic01:i-abcdefgh;bionic02:i-ijlmnop;bionic03:i-qrstuvxz" property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=bionic -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900374] [NEW] fence_aws in Focal and Bionic (LP: #1894323) don't behave the same.
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 exact same thing BUT using the "plug/port" resource argument. The thing is... in Focal, both methods work but in Bionic, the second method does not work. It is not a big deal as there are some fence agents designed to work with "pcmk_host_map" only, and some others are designed to work with "plug/port" argument. Test case (BIONIC): Using the fence-agents version from LP: #1894323 you first configure the fence_aws primitive as: ``` node 1: bionic01 node 2: bionic02 node 3: bionic03 primitive fence-bionic stonith:fence_aws \ params \ access_key="" \ secret_key="" \ region="us-east-1" \ pcmk_host_map="bionic01:i-068e134;bionic02:i-0136edd;bionic03:i-0de279ab" ``` and ``` property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=bionic ``` You can cause an issue in the interconnect and observe the fence_aws agent working properly. Then, stop the resource and remove it. Configure the fencing agent as 1 fence resource per node: ``` primitive fence-bionic01 stonith:fence_aws \ params \ access_key="" \ secret_key="" \ region="us-east-1" \ pcmk_host_map="bionic01:i-068e134;bionic02:i-0136edd;bionic03:i-0de279ab" \ plug="bionic01:i-068e134de1beddc7f" primitive fence-bionic02 stonith:fence_aws \ params \ access_key="" \ secret_key="" \ region="us-east-1" \ pcmk_host_map="bionic01:i-068e134;bionic02:i-0136edd;bionic03:i-0de279ab" \ plug="bionic02:i-0136eddd045ceb7e2" primitive fence-bionic03 stonith:fence_aws \ params \ access_key="" \ secret_key="" \ region="us-east-1" \ pcmk_host_map="bionic01:i-068e134;bionic02:i-0136edd;bionic03:i-0de279ab" \ plug="bionic03:i-0de279ab4e6d642c8" location l-fence-bionic01 fence-bionic01 -inf: bionic01 location l-fence-bionic02 fence-bionic02 -inf: bionic02 location l-fence-bionic03 fence-bionic03 -inf: bionic03 ``` This last example, using multiple fence resources, works in Focal but does not work in Bionic (after making sure both had the exact same fence_aws script version in bug LP: #1894323). I think a bisection of pacemaker between Bionic and Focal (yes, its bad because its a major version change) might be needed here to understand why using "plug" does not work in Bionic. Looks like Red Hat also faces the same issue at: https://access.redhat.com/solutions/4642491 Note: I have exhaustively tested the "pcmk_host_map" only primitive and it worked fine (fencing the correct nodes all the times I fenced the cluster). Using plug "" in Bionic is not advised as fence_aws fences other nodes (than the one provided in plug argument). ** Affects: pacemaker (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: pacemaker (Ubuntu) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900374 Title: fence_aws in Focal and Bionic (LP: #1894323) don't behave the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1900374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900016] Re: pgsql resource agent uses regexes for old crm_mon format, breaks pgsql-status and pgsql-data-status attributes
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: pgsql resource agent uses regexes for old crm_mon format, breaks pgsql-status and pgsql-data-status attributes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1900016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
(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 2020 Last change: Thu Oct 15 01:25:01 2020 by root via cibadmin on bionic01 3 nodes configured 1 resource configured Online: [ bionic01 bionic02 bionic03 ] Full list of resources: fence-bionic (stonith:fence_aws):Started bionic01 and then I fail on purpose the interconnect on node03 (bionic03): [rafaeldtinoco@bionic01 ~]$ crm status Stack: corosync Current DC: bionic01 (version 1.1.18-2b07d5c5a9) - partition with quorum Last updated: Thu Oct 15 01:26:57 2020 Last change: Thu Oct 15 01:25:01 2020 by root via cibadmin on bionic01 3 nodes configured 1 resource configured Node bionic03: UNCLEAN (offline) Online: [ bionic01 bionic02 ] Full list of resources: fence-bionic (stonith:fence_aws):Started bionic01 and the AWS console I could see machine being restarted. After bionic03 was restarted... [rafaeldtinoco@bionic01 ~]$ crm status Stack: corosync Current DC: bionic01 (version 1.1.18-2b07d5c5a9) - partition with quorum Last updated: Thu Oct 15 01:27:01 2020 Last change: Thu Oct 15 01:25:01 2020 by root via cibadmin on bionic01 3 nodes configured 1 resource configured Node bionic03: UNCLEAN (offline) Online: [ bionic01 bionic02 ] Full list of resources: fence-bionic (stonith:fence_aws):Started bionic01 I need to fix something: fence_aws agent requires python-request and python-boto3 libraries to be installed. I will have to put those as fence-agents Recommends. I have also to check a requirement on "plug" argument (as it is not really required for fence_aws to work). The way I declared the primitive was: primitive fence-bionic stonith:fence_aws \ params \ access_key= \ secret_key="" \ region=us-east-1 \ pcmk_host_map="bionic01:i-068e134de1bed;bionic02:i-0136eddd045ce;bionic03:i-0de279ab4e6d6" \ power_timeout=240 \ pcmk_reboot_timeout=480 \ pcmk_reboot_retries=4 property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=bionic -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 12:11:18 2020 * Last change: Wed Oct 14 04:38:10 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Online: [ focal01 focal02 focal03 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 [rafaeldtinoco@focal01 ~]$ crm status Cluster Summary: * Stack: corosync * Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 12:11:24 2020 * Last change: Wed Oct 14 04:38:10 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Node focal03: UNCLEAN (offline) * Online: [ focal01 focal02 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 Pending Fencing Actions: * reboot of focal03 pending: client=pacemaker-controld.444, origin=focal01 [rafaeldtinoco@focal01 ~]$ crm status Cluster Summary: * Stack: corosync * Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 12:13:59 2020 * Last change: Wed Oct 14 04:38:10 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Online: [ focal01 focal02 focal03 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
(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="" region=us-east-1 pcmk_host_map="focal01:i-034dc89cca431;focal02:i-0a160b14b40f1;focal03:i-03b6976ab0a7f" power_timeout=240 pcmk_reboot_timeout=480 pcmk_reboot_retries=4 property cib-bootstrap-options: \ have-watchdog=false \ dc-version=2.0.3-4b1f869f0f \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=focal Fencing worked as expected: [rafaeldtinoco@focal01 ~]$ crm status Cluster Summary: * Stack: corosync * Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 04:29:34 2020 * Last change: Wed Oct 14 04:28:57 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Online: [ focal01 focal02 focal03 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 [rafaeldtinoco@focal01 ~]$ crm status Cluster Summary: * Stack: corosync * Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 04:31:16 2020 * Last change: Wed Oct 14 04:28:57 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Node focal03: UNCLEAN (offline) * Online: [ focal01 focal02 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 Pending Fencing Actions: * reboot of focal03 pending: client=pacemaker-controld.3585, origin=focal01 [rafaeldtinoco@focal01 ~]$ crm status Cluster Summary: * Stack: corosync * Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Wed Oct 14 04:32:14 2020 * Last change: Wed Oct 14 04:28:57 2020 by root via cibadmin on focal01 * 3 nodes configured * 1 resource instance configured Node List: * Online: [ focal01 focal02 focal03 ] Full List of Resources: * fence-focal (stonith:fence_aws): Started focal01 And EC2 AWS console showed instance being shutdown and restarting appropriately. -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
** 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. 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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- agents/+git/fence-agents/+ref/lp1894323-bionic-v4.6.0-backport/ Like explained in the previous comment, Bionic fence-agents package does not have fence_aws... so I have backported not only the fence_aws agent inclusion from Focal (just 1 commit), but also all the fixes up to Groovy (several fixes were provided from Focal to Groovy). I'm going to test both and as for a SRU exception considering this as an "enablement". -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
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- agents/+git/fence-agents/+ref/lp1894323-focal-v4.6.0-backport/ Because of the nature of fence-agents, where they're practically isolated scripts in the form of a metadata <-> python script pair, I think it would be okay to SRU a particular agent to the latest Ubuntu version. All regression risk is confined to the agent itself and it would be easy to fix/revert if ever needed (without jeopardizing those not relying in the agent). For example, Groovy has fence-agents v4.6.0... containing all the patches needed for a good fence_aws support. I'm backporting all fixes from Groovy to Focal in this PPA. Focal had only the initial fence_aws patch, but missing all the fixes from v4.5.2 to v4.6.0. Bionic is missing all commits, including the fence_aws agent. I'm going to backport everything - the agent and fixes - to Bionic.. but it would be weird to have a more updated agent in Bionic (since it does not have the agent, it would be able to have the agent introduction with all fixes) than in Focal (that is why this SRU tries to keep both, Focal and Bionic, in the same codelevel for fence_aws). -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
@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 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
** 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 (or stop) a service, causing the police engine to take the correct decisions (like trying to start the resource somewhere else). [Test Case] * configure correctly a pacemaker cluster and add the following resources: # fencing primitive fence-focal01 stonith:fence_virsh \ params ipaddr=192.168.100.202 \ secure=true plug=focal01 login=fenceuser \ op monitor interval=30s primitive fence-focal02 stonith:fence_virsh \ params ipaddr=192.168.100.202 \ secure=true plug=focal02 login=fenceuser \ op monitor interval=30s primitive fence-focal03 stonith:fence_virsh \ params ipaddr=192.168.100.202 \ secure=true plug=focal03 login=fenceuser \ op monitor interval=30s # resources primitive virtual_ip IPaddr2 \ params ip=10.250.92.90 nic=public01 \ op monitor interval=5s primitive webserver systemd:lighttpd \ op monitor interval=5s \ op start interval=0s timeout=2s \ op stop interval=0s timeout=2s \ meta migration-threshold=2 # resource group group webserver_vip webserver virtual_ip \ meta target-role=Stopped # locations location fence-focal01-location fence-focal01 -inf: focal01 location fence-focal02-location fence-focal02 -inf: focal02 location fence-focal03-location fence-focal03 -inf: focal03 # properties property cib-bootstrap-options: \ have-watchdog=false \ dc-version=2.0.3-4b1f869f0f \ cluster-infrastructure=corosync \ stonith-enabled=on \ stonith-action=reboot \ no-quorum-policy=stop \ cluster-name=focal * Try to stop an already started resource group with "op stop timeout=2s" for the systemd resource will not be accounted as 2 seconds: Failed Resource Actions: * webserver_stop_0 on focal03 'OCF_TIMEOUT' (198): call=29, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:01:57Z', queued=1828ms, exec=204557ms * Watch the cluster collapse.. (fencing nodes, trying to start resources, fencing nodes again, and over) Increasing timeout to 20s does not help: Failed Resource Actions: * webserver_stop_0 on focal01 'OCF_TIMEOUT' (198): call=47, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:10:35Z', queued=20ms, exec=236013ms * webserver_start_0 on focal03 'OCF_TIMEOUT' (198): call=22, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:05:09Z', queued=33ms, exec=241831ms and the systemd resources startup is much less than 20 seconds. [Regression Potential] * Debian was still using ftime() for pacemaker 2.0.3, and, because of deprecation warnings, wgrant has changed it in: pacemaker (2.0.3-3ubuntu2): This was "bad" because it made this issue to appear (as we started using clock_gettime(CLOCK_MONOTONIC) instead of ftime(). But.. it was good, because in order for pacemaker to support systemd resources a monotonic clock is required (and this change enabled it). * So, there is no easy path: Its either we disable clock_gettime() support, by defining PCMK_TIME_EMERGENCY_CGT (like 2.0.3 does by default) - and stick with broken systemd resources + FTBFS - or we fix the clock_gettime() support (with this patchset) enabled by wgrant in 2.0.3. Now... to the potential issues: - * This patchset was not done in 2.0.3 because it was missed also (it is - like "half fix" for clock_gettime() was done before the release). + * After SRU review it was decided that, instead of cherry-picking the 2 + upstream merges pointed by upstream maintainer (#1992 and #1997) we + would only backport changes that affect clock_gettime() code base and + execution path. This is per SRU guidelines, trying to minimize amount of + changes to be reviewed and merged. - * The number of patches are not small but they're ALL related to the - same thing: fixing timeout not working and re-organizing timing for - resources. They're also mostly touching the same file: execd_commands.c - (and configure.ac to control macros). + * The original fix (merges #1992 and #1997) were not merged in 2.0.3 + because they were missed (it is like "half fix" for clock_gettime() was + done before the release). - * timeouts are confirmed broken for systemd resources (like the test - case shows). We could, perhaps, brake for OCF resorces and/or fencing as - well. + * There are 2 possible clocking choices for pacemaker in 2.0.3: To use + ftime() if supported (the upstream default) OR to use clock_gettime() if + selected (it becomes the
[Bug 1881762] Re: resource timeout not respecting units
** 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. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers
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. https://bugs.launchpad.net/bugs/1896223 Title: no-quorum-policy=demote and on-fail=demote features for MSSQL servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
[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 198170f66) [rafaeldtinoco@focal00 pacemaker]$ git describe upload/2.0.3-3ubuntu4 [rafaeldtinoco@focal00 pacemaker]$ git push pkg upload/2.0.3-3ubuntu4 Enumerating objects: 24, done. Counting objects: 100% (24/24), done. Delta compression using up to 8 threads Compressing objects: 100% (18/18), done. Writing objects: 100% (18/18), 14.73 KiB | 4.91 MiB/s, done. Total 18 (delta 11), reused 0 (delta 0) To ssh://git.launchpad.net/ubuntu/+source/pacemaker * [new tag] upload/2.0.3-3ubuntu4 -> upload/2.0.3-3ubuntu4 [rafaeldtinoco@focal00 ubuntu]$ debdiff pacemaker_2.0.3-3ubuntu3.dsc pacemaker_2.0.3-3ubuntu4.dsc 2>&1 | diffstat -l changelog patches/series patches/ubuntu-2.0.3-fixes/lp1881762-01-b5ff0e4-Build-finalize-restore-buildability.patch patches/ubuntu-2.0.3-fixes/lp1881762-02-1f79b43-Refactor-executor-systemd-is-no-longer-supported-without.patch patches/ubuntu-2.0.3-fixes/lp1881762-03-0772292-Fix-executor-handle-systemd-execution-times.patch patches/ubuntu-2.0.3-fixes/lp1881762-04-08e3f7e-Fix-executor-correctly-convert-ns-to-ms.patch patches/ubuntu-2.0.3-fixes/lp1881762-05-c9ce7ed-Low-executor-correctly-set-first-run-time.patch patches/ubuntu-2.0.3-fixes/lp1881762-06-9075ad9-Low-executor-record-correct-last-run-and-last-rc.patch patches/ubuntu-2.0.3-fixes/lp1881762-07-71ae72d-Refactor-executor-functionize-getting-current-time.patch [rafaeldtinoco@focal00 ubuntu]$ ls -tr1 *_source.changes | tail -1 pacemaker_2.0.3-3ubuntu4_source.changes [rafaeldtinoco@focal00 ubuntu]$ dput ubuntu pacemaker_2.0.3-3ubuntu4_source.changes Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading pacemaker_2.0.3-3ubuntu4.dsc: done. Uploading pacemaker_2.0.3-3ubuntu4.debian.tar.xz: done. Uploading pacemaker_2.0.3-3ubuntu4_source.buildinfo: done. Uploading pacemaker_2.0.3-3ubuntu4_source.changes: done. Successfully uploaded packages. -- 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
@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 respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 cibadmin on focal01 * 3 nodes configured * 5 resource instances configured Node List: * Online: [ focal01 focal02 focal03 ] Full List of Resources: * fence-focal01 (stonith:fence_virsh): Started focal02 * fence-focal02 (stonith:fence_virsh): Started focal01 * fence-focal03 (stonith:fence_virsh): Started focal01 * Resource Group: webserver_vip: * webserver (systemd:lighttpd): Started focal03 * virtual_ip(ocf::heartbeat:IPaddr2):Started focal03 The same 2s (from the test case) worked fine. -- 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
** 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 because of configuration files, or - cache to be loaded, etc). + * 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 (or stop) a service, causing the + police engine to take the correct decisions (like trying to start the + resource somewhere else). [Test Case] - - * configure correctly a pacemaker cluster and add the following resources: + + * configure correctly a pacemaker cluster and add the following + resources: # fencing primitive fence-focal01 stonith:fence_virsh \ - params ipaddr=192.168.100.202 \ - secure=true plug=focal01 login=fenceuser \ - op monitor interval=30s + params ipaddr=192.168.100.202 \ + secure=true plug=focal01 login=fenceuser \ + op monitor interval=30s primitive fence-focal02 stonith:fence_virsh \ - params ipaddr=192.168.100.202 \ - secure=true plug=focal02 login=fenceuser \ - op monitor interval=30s + params ipaddr=192.168.100.202 \ + secure=true plug=focal02 login=fenceuser \ + op monitor interval=30s primitive fence-focal03 stonith:fence_virsh \ - params ipaddr=192.168.100.202 \ - secure=true plug=focal03 login=fenceuser \ - op monitor interval=30s + params ipaddr=192.168.100.202 \ + secure=true plug=focal03 login=fenceuser \ + op monitor interval=30s # resources primitive virtual_ip IPaddr2 \ - params ip=10.250.92.90 nic=public01 \ - op monitor interval=5s + params ip=10.250.92.90 nic=public01 \ + op monitor interval=5s primitive webserver systemd:lighttpd \ - op monitor interval=5s \ - op start interval=0s timeout=2s \ - op stop interval=0s timeout=2s \ - meta migration-threshold=2 + op monitor interval=5s \ + op start interval=0s timeout=2s \ + op stop interval=0s timeout=2s \ + meta migration-threshold=2 # resource group group webserver_vip webserver virtual_ip \ - meta target-role=Stopped + meta target-role=Stopped # locations location fence-focal01-location fence-focal01 -inf: focal01 location fence-focal02-location fence-focal02 -inf: focal02 location fence-focal03-location fence-focal03 -inf: focal03 # properties property cib-bootstrap-options: \ - have-watchdog=false \ - dc-version=2.0.3-4b1f869f0f \ - cluster-infrastructure=corosync \ - stonith-enabled=on \ - stonith-action=reboot \ - no-quorum-policy=stop \ - cluster-name=focal + have-watchdog=false \ + dc-version=2.0.3-4b1f869f0f \ + cluster-infrastructure=corosync \ + stonith-enabled=on \ + stonith-action=reboot \ + no-quorum-policy=stop \ + cluster-name=focal * Try to stop an already started resource group with "op stop timeout=2s" for the systemd resource will not be accounted as 2 seconds: Failed Resource Actions: - * webserver_stop_0 on focal03 'OCF_TIMEOUT' (198): call=29, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:01:57Z', queued=1828ms, exec=204557ms + * webserver_stop_0 on focal03 'OCF_TIMEOUT' (198): call=29, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:01:57Z', queued=1828ms, exec=204557ms * Watch the cluster collapse.. (fencing nodes, trying to start resources, fencing nodes again, and over) Increasing timeout to 20s does not help: Failed Resource Actions: - * webserver_stop_0 on focal01 'OCF_TIMEOUT' (198): call=47, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:10:35Z', queued=20ms, exec=236013ms - * webserver_start_0 on focal03 'OCF_TIMEOUT' (198): call=22, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:05:09Z', queued=33ms, exec=241831ms + * webserver_stop_0 on focal01 'OCF_TIMEOUT' (198): call=47, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:10:35Z', queued=20ms, exec=236013ms + * webserver_start_0 on focal03 'OCF_TIMEOUT' (198): call=22, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:05:09Z', queued=33ms, exec=241831ms and the systemd resources startup is much less than 20 seconds. [Regression Potential] * Debian was still using ftime() for pacemaker 2.0.3, and, because of deprecation warnings, wgrant has changed it in: pacemaker (2.0.3-3ubuntu2): This was "bad" because it made this
[Bug 1881762] Re: resource timeout not respecting units
** 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 - - Clarifying why the commits were picked. Thanks for reviewing this - [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 because of configuration files, or cache to be loaded, etc). [Test Case] + + * configure correctly a pacemaker cluster and add the following resources: - * Create a pacemaker cluster with Ubuntu focal and configure a - primitive with: + # fencing - primitive haproxy systemd:haproxy \ - op monitor interval=2s \ - op start interval=0s timeout=500s \ - op stop interval=0s timeout=500s \ - meta migration-threshold=2 + primitive fence-focal01 stonith:fence_virsh \ + params ipaddr=192.168.100.202 \ + secure=true plug=focal01 login=fenceuser \ + op monitor interval=30s + primitive fence-focal02 stonith:fence_virsh \ + params ipaddr=192.168.100.202 \ + secure=true plug=focal02 login=fenceuser \ + op monitor interval=30s + primitive fence-focal03 stonith:fence_virsh \ + params ipaddr=192.168.100.202 \ + secure=true plug=focal03 login=fenceuser \ + op monitor interval=30s - or even + # resources - primitive haproxy systemd:haproxy \ - op monitor interval=2s \ - op start interval=0s timeout=500 \ - op stop interval=0s timeout=500 \ - meta migration-threshold=2 + primitive virtual_ip IPaddr2 \ + params ip=10.250.92.90 nic=public01 \ + op monitor interval=5s - and observe timeouts are not being respected. + primitive webserver systemd:lighttpd \ + op monitor interval=5s \ + op start interval=0s timeout=2s \ + op stop interval=0s timeout=2s \ + meta migration-threshold=2 + + # resource group + + group webserver_vip webserver virtual_ip \ + meta target-role=Stopped + + # locations + + location fence-focal01-location fence-focal01 -inf: focal01 + location fence-focal02-location fence-focal02 -inf: focal02 + location fence-focal03-location fence-focal03 -inf: focal03 + + # properties + + property cib-bootstrap-options: \ + have-watchdog=false \ + dc-version=2.0.3-4b1f869f0f \ + cluster-infrastructure=corosync \ + stonith-enabled=on \ + stonith-action=reboot \ + no-quorum-policy=stop \ + cluster-name=focal + + * Try to stop an already started resource group with "op stop + timeout=2s" for the systemd resource will not be accounted as 2 seconds: + + Failed Resource Actions: + * webserver_stop_0 on focal03 'OCF_TIMEOUT' (198): call=29, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:01:57Z', queued=1828ms, exec=204557ms + + * Watch the cluster collapse.. (fencing nodes, trying to start + resources, fencing nodes again, and over) + + Increasing timeout to 20s does not help: + + Failed Resource Actions: + * webserver_stop_0 on focal01 'OCF_TIMEOUT' (198): call=47, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:10:35Z', queued=20ms, exec=236013ms + * webserver_start_0 on focal03 'OCF_TIMEOUT' (198): call=22, status='Timed Out', exitreason='', last-rc-change='1970-01-01 00:05:09Z', queued=33ms, exec=241831ms + + and the systemd resources startup is much less than 20 seconds. [Regression Potential] * Debian was still using ftime() for pacemaker 2.0.3, and, because of deprecation warnings, wgrant has changed it in: pacemaker (2.0.3-3ubuntu2): This was "bad" because it made this issue to appear (as we started using clock_gettime(CLOCK_MONOTONIC) instead of ftime(). But.. it was good, because in order for pacemaker to support systemd resources a monotonic clock is required (and this change enabled it). * So, there is no easy path: Its either we disable clock_gettime() support, by defining PCMK_TIME_EMERGENCY_CGT (like 2.0.3 does by default) - and stick with broken systemd resources + FTBFS - or we fix the clock_gettime() support (with this patchset) enabled by wgrant in 2.0.3. Now... to the potential issues: * This patchset was not done in 2.0.3 because it was missed also (it is like "half fix" for clock_gettime() was done before the release). * The number of patches are not small but they're ALL related to the same thing: fixing timeout not working and re-organizing timing for resources. They're also mostly touching the same file: execd_commands.c (and configure.ac to control macros). * timeouts are confirmed broken
[Bug 1881762] Re: resource timeout not respecting units
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 nodes
Oct 01 04:09:31
Oct 01 04:09:31 Overall Results:{'success': 1, 'failure': 0, 'BadNews': 0,
'skipped': 0}
Oct 01 04:09:31
Oct 01 04:09:31 Test Summary
Oct 01 04:09:31 Test SimulStop: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Oct 01 04:09:31 TESTS COMPLETED
Nothing to worry as it wasn't a failure.
The other one, being a failure, is already expected because we don't
package cts-exec-helper command on purpose.
So, with those 2 set of tests I'm confident this fix is stable enough.
Thanks for reviewing it.
--
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:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers
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 functional/regression tests against this merge request and inform there. ** Changed in: pacemaker (Ubuntu Focal) Importance: Wishlist => Undecided ** Changed in: pacemaker (Ubuntu Focal) Status: New => In Progress -- 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: no-quorum-policy=demote and on-fail=demote features for MSSQL servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers
** 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 Title: no-quorum-policy=demote and on-fail=demote features for MSSQL servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 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 + + Clarifying why the commits were picked. Thanks for reviewing this + [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 because of configuration files, or cache to be loaded, etc). [Test Case] * Create a pacemaker cluster with Ubuntu focal and configure a primitive with: primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500s \ op stop interval=0s timeout=500s \ meta migration-threshold=2 or even primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500 \ op stop interval=0s timeout=500 \ meta migration-threshold=2 and observe timeouts are not being respected. [Regression Potential] - * Debian was still using ftime() for pacemaker 2.0.3, and, because of + * Debian was still using ftime() for pacemaker 2.0.3, and, because of deprecation warnings, wgrant has changed it in: pacemaker (2.0.3-3ubuntu2): This was "bad" because it made this issue to appear (as we started using clock_gettime(CLOCK_MONOTONIC) instead of ftime(). But.. it was good, because in order for pacemaker to support systemd resources a monotonic clock is required (and this change enabled it). - * So, there is no easy path: Its either we disable clock_gettime() + * So, there is no easy path: Its either we disable clock_gettime() support, by defining PCMK_TIME_EMERGENCY_CGT (like 2.0.3 does by default) - and stick with broken systemd resources + FTBFS - or we fix the clock_gettime() support (with this patchset) enabled by wgrant in 2.0.3. Now... to the potential issues: - * This patchset was not done in 2.0.3 because it was missed also (it is + * This patchset was not done in 2.0.3 because it was missed also (it is like "half fix" for clock_gettime() was done before the release). * The number of patches are not small but they're ALL related to the same thing: fixing timeout not working and re-organizing timing for resources. They're also mostly touching the same file: execd_commands.c (and configure.ac to control macros). - * timeouts are confirmed broken for systemd resources (like the test + * timeouts are confirmed broken for systemd resources (like the test case shows). We could, perhaps, brake for OCF resorces and/or fencing as well. - * This change has been recommended by upstream maintainer (from 2 merge + * This change has been recommended by upstream maintainer (from 2 merge numbers he pointed out in the upstream bug = https://bugs.clusterlabs.org/show_bug.cgi?id=5429). [Other Info] * Original Description (from the reporter): While working on pacemaker, i discovered a issue with timeouts haproxy_stop_0 on primary 'OCF_TIMEOUT' (198): call=583, status='Timed Out', exitreason='', last-rc-change='1970-01-04 17:21:18 -05:00', queued=44ms, exec=176272ms this lead me down the path of finding that setting a timeout unit value was not doing anything primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500s \ op stop interval=0s timeout=500s \ meta migration-threshold=2 primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500 \ op stop interval=0s timeout=500 \ meta migration-threshold=2 the two above configs result in the same behavior, pacemaker/crm seems to be ignoring the "s" I file a bug with pacemaker itself https://bugs.clusterlabs.org/show_bug.cgi?id=5429 but this lead to the following responsed, copied from the ticket:
[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers
** 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. https://bugs.launchpad.net/bugs/1896223 Title: no-quorum-policy=demote and on-fail=demote features for MSSQL servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers
** 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. https://bugs.launchpad.net/bugs/1896223 Title: [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
** 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 actions (done by the resource) don't timeout before we're expecting (sometimes starting a resource can take more time than the default time because of configuration files, or cache to be loaded, etc). [Test Case] - * Create a pacemaker cluster with Ubuntu focal and configure a + * Create a pacemaker cluster with Ubuntu focal and configure a primitive with: primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500s \ op stop interval=0s timeout=500s \ meta migration-threshold=2 or even primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500 \ op stop interval=0s timeout=500 \ meta migration-threshold=2 and observe timeouts are not being respected. [Regression Potential] - * The number of patches are not small but they're ALL related to the + * Debian was still using ftime() for pacemaker 2.0.3, and, because of + deprecation warnings, wgrant has changed it in: pacemaker + (2.0.3-3ubuntu2): + + This was "bad" because it made this issue to appear (as we started using + clock_gettime(CLOCK_MONOTONIC) instead of ftime(). But.. it was good, + because in order for pacemaker to support systemd resources a monotonic + clock is required (and this change enabled it). + + * So, there is no easy path: Its either we disable clock_gettime() + support, by defining PCMK_TIME_EMERGENCY_CGT (like 2.0.3 does by + default) - and stick with broken systemd resources + FTBFS - or we fix + the clock_gettime() support (with this patchset) enabled by wgrant in + 2.0.3. + + Now... to the potential issues: + + * This patchset was not done in 2.0.3 because it was missed also (it is + like "half fix" for clock_gettime() was done before the release). + + * The number of patches are not small but they're ALL related to the same thing: fixing timeout not working and re-organizing timing for - resources. + resources. They're also mostly touching the same file: execd_commands.c + (and configure.ac to control macros). - * TBD (more info to come) + * timeouts are confirmed broken for systemd resources (like the test + case shows). We could, perhaps, brake for OCF resorces and/or fencing as + well. + + * This change has been recommended by upstream maintainer (from 2 merge + numbers he pointed out in the upstream bug = + https://bugs.clusterlabs.org/show_bug.cgi?id=5429). [Other Info] - - * Original Description (from the reporter): + + * Original Description (from the reporter): While working on pacemaker, i discovered a issue with timeouts haproxy_stop_0 on primary 'OCF_TIMEOUT' (198): call=583, status='Timed Out', exitreason='', last-rc-change='1970-01-04 17:21:18 -05:00', queued=44ms, exec=176272ms this lead me down the path of finding that setting a timeout unit value was not doing anything primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500s \ op stop interval=0s timeout=500s \ meta migration-threshold=2 primitive haproxy systemd:haproxy \ op monitor interval=2s \ op start interval=0s timeout=500 \ op stop interval=0s timeout=500 \ meta migration-threshold=2 the two above configs result in the same behavior, pacemaker/crm seems to be ignoring the "s" I file a bug with pacemaker itself https://bugs.clusterlabs.org/show_bug.cgi?id=5429 but this lead to the following responsed, copied from the ticket:
[Bug 1881762] Re: resource timeout not respecting units
** 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 (Ubuntu Focal) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: pacemaker (Ubuntu Focal) Importance: Undecided => High ** Changed in: pacemaker (Ubuntu Focal) Status: New => In Progress ** Tags added: server-next ** Merge proposal unlinked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391397 -- 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
** 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 because of configuration files, or + cache to be loaded, etc). + + [Test Case] + + * Create a pacemaker cluster with Ubuntu focal and configure a + primitive with: + + primitive haproxy systemd:haproxy \ + op monitor interval=2s \ + op start interval=0s timeout=500s \ + op stop interval=0s timeout=500s \ + meta migration-threshold=2 + + or even + + primitive haproxy systemd:haproxy \ + op monitor interval=2s \ + op start interval=0s timeout=500 \ + op stop interval=0s timeout=500 \ + meta migration-threshold=2 + + and observe timeouts are not being respected. + + [Regression Potential] + + * The number of patches are not small but they're ALL related to the + same thing: fixing timeout not working and re-organizing timing for + resources. + + * TBD (more info to come) + + [Other Info] + + * Original Description (from the reporter): + While working on pacemaker, i discovered a issue with timeouts haproxy_stop_0 on primary 'OCF_TIMEOUT' (198): call=583, status='Timed Out', exitreason='', last-rc-change='1970-01-04 17:21:18 -05:00', queued=44ms, exec=176272ms this lead me down the path of finding that setting a timeout unit value was not doing anything primitive haproxy systemd:haproxy \ - op monitor interval=2s \ - op start interval=0s timeout=500s \ - op stop interval=0s timeout=500s \ - meta migration-threshold=2 + op monitor interval=2s \ + op start interval=0s timeout=500s \ + op stop interval=0s timeout=500s \ + meta migration-threshold=2 primitive haproxy systemd:haproxy \ - op monitor interval=2s \ - op start interval=0s timeout=500 \ - op stop interval=0s timeout=500 \ - meta migration-threshold=2 + op monitor interval=2s \ + op start interval=0s timeout=500 \ + op stop interval=0s timeout=500 \ + meta migration-threshold=2 - the two above configs result in the same behaviour, pacemaker/crm seems to be ignoring the "s" + the two above configs result in the same behavior, pacemaker/crm seems + to be ignoring the "s" + I file a bug with pacemaker itself https://bugs.clusterlabs.org/show_bug.cgi?id=5429 but this lead to the following responsed, copied from the ticket:
[Bug 1881762] Re: resource timeout not respecting units
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 - lp1881762-0002-6a6ba482-Build-finalize-restore-buildability-in-the-face-of-o.patch - lp1881762-0003-720b9d53-Build-configure-fix-syntax-error.patch - lp1881762-0004-7f07480c-Low-configure-missing-monotonic-clock-isn-t-fatal-fo.patch - lp1881762-0005-794aad8b-Log-executor-improve-process-completion-message.patch - lp1881762-0006-441dc18e-Refactor-executor-systemd-is-no-longer-supported-wit.patch - lp1881762-0007-dd1756c2-Fix-executor-handle-systemd-execution-times-under-1-.patch - lp1881762-0008-7969c205-Fix-executor-correctly-convert-nanoseconds-to-millis.patch - lp1881762-0009-310616af-Low-executor-correctly-set-first-run-time.patch - lp1881762-0010-e0f20f51-Low-executor-record-correct-last-run-and-last-rc-cha.patch - lp1881762-0011-a3050274-Refactor-executor-functionize-getting-current-time-i.patch And they come from the fixes mentioned from upstream maintainer (merges #1992 and #1997, and some other pre requirements). Let's see how that goes, you can test this hotfix from: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1881762 once it is finished building. I'll link a merge request to this public bug so it gets reviewed by another engineer from ubuntu server team before we ask for the SRU. Let me know if the fix is not good (any time) and I'll provide you something else. Cheers o/ -- 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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 Gaillot Date: Thu Feb 27 00:24:38 2020 Merge pull request #1997 from kgaillot/times Fix regression in reported last run / rc change times in status displays And Ken Gaillot suggested in upstream bug. After PPA is ready, I'll do the SRU and we can lower priority as it will depend on the SRU process. -- 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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
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: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key)
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 Fix => Invalid ** Changed in: fence-agents (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: fence-agents (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864404 Title: fence_scsi and fence_mpath configuration issues (e.g. /var/run/cluster/fence_scsi.key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
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 issues. I see that this has been assigned to @slashd. Eric, Important thing here is to have netplan fix in focal (as it is the latest LTS) in order for HA to be supported with it. KeepConfiguration= is good enough, for now, if using systemd-networkd only. Thank you! ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
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. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04
** 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 long iscsi target names in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892292] Re: iscsi boot fails to boot into rootfs
** 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 boot into rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1892292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql server)
** 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. https://bugs.launchpad.net/bugs/1896223 Title: [FFe] this is the no-quorum-policy feature (specially for mssql server) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
$ ./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 04:40:29 Scenario: Every Test Once
Sep 24 04:40:29 CTS Master: 10.250.97.104
Sep 24 04:40:29 CTS Logfile:/home/rafaeldtinoco/cts.log
Sep 24 04:40:29 Random Seed:1600922428
Sep 24 04:40:29 Syslog variant: rsyslog
Sep 24 04:40:29 System log files: /var/log/messages
Sep 24 04:40:29 Cluster starts at boot: 1
Sep 24 04:40:29 Cluster nodes:
Sep 24 04:40:29 * groovy01
Sep 24 04:40:29 * groovy02
Sep 24 04:40:29 * groovy03
Sep 24 04:40:32 Writing log with key: 02c86ca5-acb3-4498-bfa6-726a53b23da6
Sep 24 04:40:32 Testing for combined syslog logs
Sep 24 04:40:38 Testing for journal logs
Sep 24 04:40:39 Continuing with journal-based log reader
Sep 24 04:40:45 Stopping crm-corosync on node groovy01
Sep 24 04:40:50 Stopping crm-corosync on node groovy02
Sep 24 04:40:55 Stopping crm-corosync on node groovy03
Sep 24 04:40:57 Starting Cluster Manager on all nodes.
Sep 24 04:40:59 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy02
Sep 24 04:41:29 Starting crm-corosync on node groovy03
Sep 24 04:41:50 Running test Flip (groovy03)[ 1]
Sep 24 04:42:34 Running test Restart(groovy01)[ 2]
Sep 24 04:43:00 Running test Stonithd (groovy03)[ 3]
Sep 24 04:44:07 Running test StartOnebyOne (groovy03)[ 4]
Sep 24 04:46:29 Running test SimulStart (groovy02)[ 5]
Sep 24 04:47:23 Running test SimulStop (groovy03)[ 6]
Sep 24 04:47:39 Running test StopOnebyOne (groovy03)[ 7]
Sep 24 04:48:44 Running test RestartOnebyOne(groovy02)[ 8]
Sep 24 04:50:23 Running test PartialStart (groovy03)[ 9]
Sep 24 04:51:08 Running test Standby(groovy02)[ 10]
Sep 24 04:52:03 Running test MaintenanceMode(groovy01)[ 11]
Sep 24 04:52:26 Running test ResourceRecover(groovy03)[ 12]
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r
fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r
fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r
fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Test ResourceRecoverFAILED: fence-groovy01 was
not recovered and is inactive
Sep 24 04:52:41 Running test Reattach (groovy03)[ 13]
Sep 24 04:54:03 Running test SpecialTest1 (groovy02)[ 14]
Sep 24 04:55:05 Running test NearQuorumPoint(groovy02)[ 15]
Sep 24 04:55:20 Stopping Cluster Manager on all nodes
Sep 24 04:55:20 Stopping crm-corosync on node groovy03
Sep 24 04:55:28
Sep 24 04:55:28 Overall Results:{'success': 14, 'failure': 1, 'BadNews': 0,
'skipped': 0}
Sep 24 04:55:28
Sep 24 04:55:28 Test Summary
Sep 24 04:55:28 Test Flip:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test Restart: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test Stonithd:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test StartOnebyOne: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test SimulStart: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test SimulStop: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test StopOnebyOne:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test RestartOnebyOne: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test PartialStart:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test Standby: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test MaintenanceMode: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test ResourceRecover: {'calls': 1, 'failure': 1, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test Reattach:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test SpecialTest1:{'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 Test NearQuorumPoint: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Sep 24 04:55:28 TESTS COMPLETED
The test that fails does it because we have a debian patch removing
"cts-exec-helper" from the Debian
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
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 - [2019-13-01 00:00:00Z/P1M] * Passed: iso8601- Invalid period - [20191077T15/P1M] * Passed: iso8601- Invalid period - [2019-10-01T25:00:00Z/P1M] * Passed: iso8601- Invalid period - [2019-10-01T24:00:01Z/P1M] * Passed: iso8601- Invalid period - [PT5H/20191001T007000Z] * Passed: iso8601- Invalid period - [2019-10-01 00:00:80Z/P1M] * Passed: iso8601- Invalid period - [2019-10-01 00:00:10 +25:00/P1M] * Passed: iso8601- Invalid period - [20191001T10 -00:61/P1M] * Passed: iso8601- Invalid period - [P1Y/2019-02-29 00:00:00Z] * Passed: iso8601- Invalid period - [2019-01-01 00:00:00Z/P] * Passed: iso8601- Invalid period - [P1Z/2019-02-20 00:00:00Z] * Passed: iso8601- Invalid period - [P1YM/2019-02-20 00:00:00Z] * Passed: iso8601- 2014-01-01 00:30:00 - 1 Hour * Passed: iso8601- Valid date - Feb 29 in leap year * Passed: iso8601- Valid date - using 'T' and offset * Passed: iso8601- 24:00:00 equivalent to 00:00:00 of next day * Passed: iso8601- 2006-W01-7 * Passed: iso8601- 2006-W01-7 - round-trip * Passed: iso8601- 2006-W01-1 * Passed: iso8601- 2006-W01-1 - round-trip * Passed: iso8601- 2007-W01-7 * Passed: iso8601- 2007-W01-7 - round-trip * Passed: iso8601- 2007-W01-1 * Passed: iso8601- 2007-W01-1 - round-trip * Passed: iso8601- 2008-W01-7 * Passed: iso8601- 2008-W01-7 - round-trip * Passed: iso8601- 2008-W01-1 * Passed: iso8601- 2008-W01-1 - round-trip * Passed: iso8601- 2009-W01-7 * Passed: iso8601- 2009-W01-7 - round-trip * Passed: iso8601- 2009-W01-1 * Passed: iso8601- 2009-W01-1 - round-trip * Passed: iso8601- 2010-W01-7 * Passed: iso8601- 2010-W01-7 - round-trip * Passed: iso8601- 2010-W01-1 * Passed: iso8601- 2010-W01-1 - round-trip * Passed: iso8601- 2011-W01-7 * Passed: iso8601- 2011-W01-7 - round-trip * Passed: iso8601- 2011-W01-1 * Passed: iso8601- 2011-W01-1 - round-trip * Passed: iso8601- 2012-W01-7 * Passed: iso8601- 2012-W01-7 - round-trip * Passed: iso8601- 2012-W01-1 * Passed: iso8601- 2012-W01-1 - round-trip * Passed: iso8601- 2013-W01-7 * Passed: iso8601- 2013-W01-7 - round-trip * Passed: iso8601- 2013-W01-1 * Passed: iso8601- 2013-W01-1 - round-trip * Passed: iso8601- 2014-W01-7 * Passed: iso8601- 2014-W01-7 - round-trip * Passed: iso8601- 2014-W01-1 * Passed: iso8601- 2014-W01-1 - round-trip * Passed: iso8601- 2015-W01-7 * Passed: iso8601- 2015-W01-7 - round-trip * Passed: iso8601- 2015-W01-1 * Passed: iso8601- 2015-W01-1 - round-trip * Passed: iso8601- 2016-W01-7 * Passed: iso8601- 2016-W01-7 - round-trip * Passed: iso8601- 2016-W01-1 * Passed: iso8601- 2016-W01-1 - round-trip * Passed: iso8601- 2017-W01-7 * Passed: iso8601- 2017-W01-7 - round-trip * Passed: iso8601- 2017-W01-1 * Passed: iso8601- 2017-W01-1 - round-trip * Passed: iso8601- 2018-W01-7 * Passed: iso8601- 2018-W01-7 - round-trip * Passed: iso8601- 2018-W01-1 * Passed: iso8601- 2018-W01-1 - round-trip * Passed: iso8601- 2040-W01-7 * Passed: iso8601- 2040-W01-7 - round-trip * Passed: iso8601- 2040-W01-1 * Passed: iso8601- 2040-W01-1 - round-trip * Passed: iso8601- 2009-W53-07 * Passed: iso8601- epoch + 2 Years 5 Months 6 Minutes * Passed: iso8601- 2009-01-31 + 1 Month * Passed: iso8601- 2009-01-31 + 2 Months * Passed: iso8601- 2009-01-31 + 3 Months * Passed: iso8601- 2009-03-31 - 1 Month * Passed: iso8601- 2038-01-01 + 3 Months * Passed: cibadmin - Validate CIB * Passed: crm_attribute - Configure something before erasing * Passed: cibadmin - Require --force for CIB erasure * Passed: cibadmin - Allow CIB erasure with --force * Passed: cibadmin - Query CIB * Passed: crm_attribute - Set cluster option * Passed: cibadmin - Query new cluster option * Passed: cibadmin - Query cluster options * Passed: crm_attribute - Set no-quorum policy * Passed: cibadmin - Delete nvpair * Passed: cibadmin - Create operation should fail * Passed: cibadmin - Modify cluster options section * Passed: cibadmin - Query updated cluster option * Passed: crm_attribute - Set duplicate cluster option * Passed: crm_attribute - Setting multiply defined cluster option should fail * Passed: crm_attribute
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
** 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
I see that AWS has 2 fencing mechanisms: - fence_aws using boto3 library (in fence-agents) - fence_ec2 (in cluster-glue) Bug: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1895355 has brought fence_ec2 support to our cluster-glue package by backporting needed patches. Perhaps 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) => (unassigned) ** Changed in: fence-agents (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: fence-agents (Ubuntu Focal) Importance: Undecided => Wishlist -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896696] [NEW] Backport fence_ec2 support to Focal and Bionic
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 supported parameters [76138dfb Medium: external/ec2: Mitigate fence race (bsc#1088656) 6734e0d0 High: external/ec2: Avoid unicode errors and improve performance (bsc#1088656) ba5710b3 Dev: external/ec2: Clean up whitespace 609cc386 Fix: stonith:external/ec2: Enforce en_US.UTF-8 locale when invoking aws client (bsc#1059171) 0f081f69 Medium: stonith: external/ec2: use target's uname as default for port 291a4378 Dev: stonith: external/ec2: protect unknown_are_stopped expansion 5cd5ffd2 Dev: stonith: external/ec2: add unknown_are_stopped to getconfignames 289e8fd3 Low: stonith: external/ec2: update name in the short description b7bed186 Dev: update permissions for ec2 de5e068d High: stonith: external/ec2: new agent for aws/ec2 This bug is an attempt of backporting the agent to Focal and Bionic (LTS releases). ** Affects: cluster-glue (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: cluster-glue (Ubuntu Bionic) Importance: Wishlist Status: Confirmed ** Affects: cluster-glue (Ubuntu Focal) Importance: Wishlist Status: Confirmed ** Also affects: cluster-glue (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cluster-glue (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: cluster-glue (Ubuntu) Status: New => Fix Released ** Changed in: cluster-glue (Ubuntu Bionic) Status: New => Confirmed ** Changed in: cluster-glue (Ubuntu Focal) Status: New => Confirmed ** Changed in: cluster-glue (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: cluster-glue (Ubuntu Focal) Importance: Undecided => Wishlist ** Description changed: 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 - [FFE] 7c84a6ae Fix EC2 stonith plugin - [FFE] 27e83692 Fix: stonith:ibmhmc: Add "managedsyspat" and "password" as supported parameters - [FFE] 76138dfb Medium: external/ec2: Mitigate fence race (bsc#1088656) - [FFE] 6734e0d0 High: external/ec2: Avoid unicode errors and improve performance (bsc#1088656) - [FFE] ba5710b3 Dev: external/ec2: Clean up whitespace - [FFE] 609cc386 Fix: stonith:external/ec2: Enforce en_US.UTF-8 locale when invoking aws client (bsc#1059171) - [FFE] 0f081f69 Medium: stonith: external/ec2: use target's uname as default for port - [FFE] 291a4378 Dev: stonith: external/ec2: protect unknown_are_stopped expansion - [FFE] 5cd5ffd2 Dev: stonith: external/ec2: add unknown_are_stopped to getconfignames - [FFE] 289e8fd3 Low: stonith: external/ec2: update name in the short description - [FFE] b7bed186 Dev: update permissions for ec2 - [FFE] de5e068d High: stonith: external/ec2: new agent for aws/ec2 + 7c84a6ae Fix EC2 stonith plugin + 27e83692 Fix: stonith:ibmhmc: Add "managedsyspat" and "password" as supported parameters + [76138dfb Medium: external/ec2: Mitigate fence race (bsc#1088656) + 6734e0d0 High: external/ec2: Avoid unicode errors and improve performance (bsc#1088656) + ba5710b3 Dev: external/ec2: Clean up whitespace + 609cc386 Fix: stonith:external/ec2: Enforce en_US.UTF-8 locale when invoking aws client (bsc#1059171) + 0f081f69 Medium: stonith: external/ec2: use target's uname as default for port + 291a4378 Dev: stonith: external/ec2: protect unknown_are_stopped expansion + 5cd5ffd2 Dev: stonith: external/ec2: add unknown_are_stopped to getconfignames + 289e8fd3 Low: stonith: external/ec2: update name in the short description + b7bed186 Dev: update permissions for ec2 + de5e068d High: stonith: external/ec2: new agent for aws/ec2 This bug is an attempt of backporting the agent to Focal and Bionic (LTS releases). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896696 Title: Backport fence_ec2 support to Focal and Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1896696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)
** No longer affects: fence-agents (Ubuntu Groovy) ** Also affects: fence-agents (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: fence-agents (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: fence-agents (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: fence-agents (Ubuntu Bionic) 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/1889070 Title: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894323] Re: Add fence_aws fencing from v4.6.0 agent to Bionic
In bug: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894325 I have synced v4.6.0-1 recently from Debian, and it includes fence_aws and fence_ibmz: - fence_aws agent being backported to Bionic (LP: #1894323) - Add LPAR fence agent to Pacemaker (LP: #1889070) So in this bug we should backport fence_aws to Focal and Bionic, if possible. -- 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: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Thanks a lot for catching up with this @mfo. And Richard for all the tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
The feature was announced by the following e-mail: 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: Cluster Labs - All topics related to open-source clustering welcomed Hi all, Looking ahead to the Pacemaker 2.0.5 release expected at the end of this year, here is a new feature already in the master branch. When configuring resource operations, Pacemaker lets you set an "on- fail" policy to specify whether to restart the resource, fence the node, etc., if the operation fails. With 2.0.5, a new possible value will be "demote", which will mean "demote this resource but do not fully restart it". "Demote" will be a valid value only for promote actions, and for recurring monitors with "role" set to "Master". Once the resource is demoted, it will be eligible for promotion again, so if the promotion scores have not changed, a promote on the same node may be attempted. If this is not desired, the agent can change the promotion scores either in the failed monitor or the demote. The intended use case is an application where a successful demote assures a well-functioning service, and a full restart would be unnecessarily heavyweight. A large database might be an example. Similarly, Pacemaker offers the cluster-wide "no-quorum-policy" option to specify what happens to resources when quorum is lost (the default being to stop them). With 2.0.5, "demote" will be a possible value here as well, and will mean "demote all promotable resources and stop all other resources". The intended use case is an application that cannot cause any harm after being demoted, and may be useful in a demoted role even if there is no quorum. A database that operates read-only when demoted and doesn't depend on any non-promotable resources might be an example. Happy clustering :) -- Ken Gaillot ** Description changed: In bug: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1895883 I did the stabilization patches for pacemaker 2.0.4.. and I did not merge this feature so it could have its own FFe (this bug). The following patch-set: * this is the no-quorum-policy feature microsoft needs for mssqlserver |\ | * c4429d86e - Log: scheduler: downgrade "active on" messages to trace (3 mont | * 7eec572db - Build: libcrmcommon: bump CRM feature set (3 months ago) Wishlist ** Changed in: pacemaker (Ubuntu) Importance: Undecided => High -- 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
I'm now running all pacemaker cluster test suite on this pacemaker (together with latest changes in all HA stack for Groovy). Will make sure there are no regressions in this version AND this package will continue being maintained by Ubuntu Server team. -- 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
Release team, I would like this to be an exception so I can add a new feature to pacemaker: the on-fail="demote" recovery policy for the pacemaker policy engine. -- 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
* Post 2.0.4 feature backport: on-fail="demote" recovery policy (LP: #1896223) debian/patches/ubuntu/lp1896223-*: - [c4429d86e] Log: scheduler: downgrade "active on" messages to trace - [01c5ec67e] Low: scheduler: match initial no-quorum-policy struct value to - [015b5c012] Doc: Pacemaker Explained: document no-quorum-policy=demote - [5d809e136] Test: scheduler: add regression test - [b1ae35938] Feature: scheduler: support "demote" choice - [0b6834453] Refactor: scheduler: functionize checking quorum policy - [d4b9117e7] Doc: Pacemaker Explained: correct on-fail default - [204961e95] Doc: Pacemaker Explained: document new on-fail="demote" option - [d29433ea5] Test: scheduler: add regression tests for on-fail="demote" - [874f75e0f] Feature: scheduler: new on-fail="demote" recovery policy - [2f1e2df1f] Feature: xml: add on-fail="demote" option to resources schema - [fd55a6660] Doc: libpacemaker: improve comments for resource state - [98c3b649f] Log: libpacemaker: check for re-promotes specifically - [ff6aebecf] Doc: libpacemaker: improve comments when logging actions - [f2d244bc4] Test: scheduler: test forcing a restart instead of reload - [a4d6a20a9] Low: libpacemaker: don't force stop when skipping reload - [8dceba792] Refactor: scheduler: use more appropriate types in a couple - [ef246ff05] Fix: scheduler: disallow on-fail=stop for stop operations - [f1f71b3f3] Refactor: scheduler: functionize comparing on-fail values -- 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890185] Re: scheduler: support/backport on-fail="demote" recovery policy for promoted resources
*** This bug is a duplicate of bug 1896223 *** https://bugs.launchpad.net/bugs/1896223 ** This bug has been marked a duplicate of bug 1896223 [FFe] this is the no-quorum-policy feature (specially for mssql sevrer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890185 Title: scheduler: support/backport on-fail="demote" recovery policy for promoted resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1890185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] Re: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
This is the same as: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1890185 -- 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] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895647] Re: containerd-shim deadlocks, then crashes
Hello Marius, Thank you for taking the time to file a bug report. Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". I know you had trouble in getting the strace output already but, if you don't mind, could you please provide us a short reproducer ? This way me or some other person is able to reproduce it locally and chose preferred tools to debug the issue. Please change status back to New once you're done so this can be triaged again by someone from the Ubuntu Server team. Thanks a lot. -rafaeldtinoco ** Changed in: containerd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895647 Title: containerd-shim deadlocks, then crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1895647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896223] [NEW] [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
Public bug reported: In bug: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1895883 I did the stabilization patches for pacemaker 2.0.4.. and I did not merge this feature so it could have its own FFe (this bug). The following patch-set: * this is the no-quorum-policy feature microsoft needs for mssqlserver |\ | * c4429d86e - Log: scheduler: downgrade "active on" messages to trace (3 mont | * 7eec572db - Build: libcrmcommon: bump CRM feature set (3 months ago) https://bugs.launchpad.net/bugs/1896223 Title: [FFe] this is the no-quorum-policy feature (specially for mssql sevrer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
