le to none; this affects the test case only.
** Affects: libgnupg-interface-perl (Ubuntu)
Importance: Undecided
Assignee: Heitor Alves de Siqueira (halves)
Status: Fix Released
** Affects: libgnupg-interface-perl (Ubuntu Bionic)
Importance: Low
Assignee: Heitor Alv
Failures for libgnupg-interface-perl are the result of the upstream test
suite and very unlikely to be related to this SRU. I've opened bug
1916499 to investigate those separately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Autopkgtest failures for gnupg2 on armhf have been fixed with a re-run,
so it was likely due to a flaky testbed setup.
Failures for libgnupg-interface-perl are the result of the upstream test
suite and very unlikely to be related to this SRU. I've opened bug
1916499 to investigate those separately
** Changed in: zfs-linux (Ubuntu Hirsute)
Status: In Progress => Fix Released
** Changed in: zfs-linux (Ubuntu Hirsute)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
** Description changed:
[Impact]
TXG sync stalls, causing ZFS workloads to hang indefi
I've pushed some test kernels for X/B to a public PPA assigned to this
bug [0], hopefully it'll make validating the upstream patch a bit
easier.
[0] https://launchpad.net/~halves/+archive/ubuntu/lp1772675
** Changed in: linux (Ubuntu Xenial)
Importance: Low => High
** Changed in: linux (Ubunt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916486
Title:
zfs_zrele_async can cause txg sync deadlocks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-
** Patch added: "lp1916486-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471918/+files/lp1916486-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Patch added: "lp1916486-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471919/+files/lp1916486-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Patch added: "lp1916486-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471920/+files/lp1916486-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "lp1916486-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471921/+files/lp1916486-groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Description changed:
[Impact]
TXG sync stalls, causing ZFS workloads to hang indefinitely
[Description]
For certain ZFS workloads, we can see hung task timeouts in the kernel logs
due to a transaction group deadlock. Userspace process will hang and display
stack traces similar to t
** Description changed:
[Impact]
On AMD Zen systems, memcpy() calls see a heavy performance regression in
Focal and Groovy, due to the way __x86_non_temporal_threshold is calculated.
- Before 'glibc-2.33~455', cache values were calculated taking into
consideration the number of hardware t
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
** Changed in: lvm2 (Ubuntu)
Status: New => Fix Released
** Also affects: lvm2 (Ubuntu Focal)
Importance: Undecided
Below is the same benchmark from the case description, validating the
performance regression on Groovy. Patched glibc builds for both Focal
and Groovy amd64/i386 are available at ppa:halves/lp1928508-test [0].
$ hyperfine -n groovy-2.32-0ubuntu3 'lxc exec groovy ./test_memcpy64 32' -n
groovy-patc
I've ran the same test on an Intel system, to ensure we aren't
introducing any regressions there. Besides basic smoke tests, the
benchmarks from the description showed that the performance on Intel is
not significantly affected by this patch.
halves@rotom:~$ head -n5 /proc/cpuinfo
processor
** Patch added: "lp1928508-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502960/+files/lp1928508-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Patch added: "lp1928508-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502961/+files/lp1928508-groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Patch removed: "lp1928508-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502960/+files/lp1928508-focal.debdiff
** Patch removed: "lp1928508-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502961/+files/l
** Patch added: "lp1928508-groovy-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5503158/+files/lp1928508-groovy-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Changed in: sosreport (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => Heitor Alves de Siqueira (halves)
** Changed in: sosreport (Ubuntu Focal)
Assignee: Eric Desrochers (slashd) => Heitor Alves de Siqueira (halves)
** Changed in: sosreport (Ubuntu Groovy)
Assignee
** Changed in: sosreport (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Focal)
Importance: Undecided =>
** Description changed:
[Impact]
On AMD Zen systems, memcpy() calls see a heavy performance regression in
Focal and Groovy, due to the way __x86_non_temporal_threshold is calculated.
Before 'glibc-2.33~455', cache values were calculated taking into
consideration the number of hardware
** Description changed:
[Impact]
sos's networking plugin may trigger the devlink kernel module to load.
We don't want sos to modify/change/alter the state of a machine
whatsoever, especially during troubleshooting. But it may be the case
for the networking plugin, depending on the run
There's currently a pending SRU for glibc on Groovy, which I based my
debdiff on. Although that SRU has already cleared the 7 day grace
period, there are still a few pending bugs for verification which we
would need to clear before being able to upload a fix for this one.
Since Groovy is going EOL
Since we don't have a reliable test procedure for triggering the KVM
emulation failures, I did basic smoke tests on VMs using seabios from
mitaka-proposed. Things look good, and general NMI functionality seems
to be working correctly.
I've also confirmed with affected users that this version has f
We've determined this to be due to using disks with mixed sector sizes
(i.e. different physical and logical sector sizes). The mentioned patch
[0] enables lvmlockd to create shared leases in mixed sector sized
disks, but additional support is needed in sanlock for these to work
correctly.
The requ
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
+
+ [Test Plan]
+ 1. Install Ubuntu 20.04 using ZFS-on-root
+ 2. Add encrypted partition to /etc/crypttab:
+swap/dev/nvme0n1p1 /dev/urandom
** Patch added: "lp1923661-b.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510563/+files/lp1923661-b.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Patch added: "lp1923661-f.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510564/+files/lp1923661-f.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Patch added: "lp1923661-h.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510566/+files/lp1923661-h.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Patch added: "lp1923661-g.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510565/+files/lp1923661-g.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
abios | 1.8.2-1ubuntu1 | xenial | source, all
seabios | 1.10.2-1ubuntu1 | bionic | source, all
Releases starting with Bionic already have this fix.
[0]
https://review.coreboot.org/plugins/gitiles/seabios/+/3156b71a535e661%5E%21/#F0
** Affects: seabios (Ubuntu)
Importance: High
** Changed in: seabios (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: seabios (Ubuntu Xenial)
Status: Confirmed => In Progress
** Patch added: "lp1927547-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1927547/+attachment/5497091/+files/lp
** Patch added: "lp1927547-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1927547/+attachment/5497092/+files/lp1927547-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Fixes are now available under the "ESM Infrastructure Security" PPA for
Trusty and Xenial, according to the versions below:
Trusty -- 1.7.4-4ubuntu1+esm1
Xenial -- 1.8.2-1ubuntu1+esm1
** Changed in: seabios (Ubuntu Trusty)
Status: In Progress => Fix Released
** Changed in: seabios (Ubunt
hanged in: cloud-archive/mitaka
Importance: Undecided => High
** Changed in: cloud-archive/mitaka
Status: New => Confirmed
** Changed in: cloud-archive/mitaka
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: cloud-archive
Assignee: (unassi
roovy-proposed | source
glibc | 2.33-0ubuntu5 | hirsute | source
Affected releases include Ubuntu Focal and Groovy. Bionic is not
affected, and releases starting with Hirsute already ship the upstream
patch to fix this regression.
** Affects: glibc (Ubuntu)
Importance: High
Assigne
** Attachment added: "test_memcpy.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5497631/+files/test_memcpy.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928508
Tit
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920047
Title:
sanlock global lock creation fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
** Description changed:
[Impact]
Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
[Test Plan]
1. Install Ubuntu 20.04 using ZFS-on-root
2. Add encrypted partition to /etc/crypttab:
-swap/dev/nvme0n1p1 /dev/urandom
Verified Bionic according to test case from description:
root@b-sos:~# dpkg -l | grep sosreport
ii sosreport4.1-1ubuntu0.18.04.3
amd64Set of tools to gather troubleshooting data from a system
root@b-sos:~# lsmod | grep -i devlink
root@b-sos:
Verified Focal according to test case from description:
root@f-sos:~# dpkg -l | grep sosreport
ii sosreport 4.1-1ubuntu0.20.04.3 amd64
Set of tools to gather troubleshooting data from a system
root@f-sos:~# lsmod | grep -i devlink
root@f-sos:~# sos re
Verified Hirsute according to test case from description:
root@h-sos:~# dpkg -l | grep sos
ii sosreport 4.1-1ubuntu1.2
amd64Set of tools to gather troubleshooting
data from a system
root@h-sos:~# lsmod | grep -i
Public bug reported:
[Impact]
Atari partition tables have very broad specifications, and can spontaneously
show up on uncleared disks with "garbage" data. There have been reports of
misinterpreted AHDI partition tables before (see [0] and [1]), usually as an
unintended side-effect of using non-
** Description changed:
[Impact]
- Atari partition tables have very broad specifications, and can spontaneously
- show up on uncleared disks with "garbage" data. There have been reports of
- misinterpreted AHDI partition tables before (see [0] and [1]), usually as an
- unintended side-effect of
t; Confirmed
** Changed in: linux-aws (Ubuntu Xenial)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux-aws (Ubuntu Bionic)
Assignee: (unassigned)
** Description changed:
[Impact]
Atari partition tables have very broad specifications, and can spontaneously
show up on uncleared disks with "garbage" data. There have been reports of
misinterpreted AHDI partition tables before (see [0] and [1]), usually as an
unintended side-effect of usi
Patches sent to the kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2020-December/115633.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908264
Title:
Disable Atari partition sup
debdiff v2 with fixed author information
** Patch added: "v2-lp1821343-disco.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254440/+files/v2-lp1821343-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "lp1821343-xenial.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254688/+files/lp1821343-xenial.debdiff
** Patch removed: "lp1821343-disco.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254240/+fi
** Patch added: "lp1821343-cosmic.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254686/+files/lp1821343-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Patch added: "lp1821343-bionic.debdiff"
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254687/+files/lp1821343-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
[Impact]
- Performance degradation for read/write workloads in bcache devices,
occasional system stalls
+ Querying bcache's priority_stats attribute in sysfs causes severe performance
degradation for read/write workloads and occasional system stalls
+
+ [Test Case]
+ N
Patches sent to kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2019-October/104658.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840043
Title:
bcache: Performance degradation
Upstream commit:
https://git.kernel.org/linus/d55a4ae9e1af
** Changed in: linux
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
[Impact]
Some wireless Intel cards that use the iwlmvm driver are not available during
installation.
[Test Case]
Boot up the Ubuntu installer on a system with an iwlmvm adapter, and try using
the wireless connection.
[Fix]
Add the missing sub-module to debian.master/d-i/ni
Patch sent to kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2019-October/104710.html
** Description changed:
[Impact]
Some wireless Intel cards that use the iwlmvm driver are not available during
installation.
[Test Case]
Boot up the Ubuntu installer on a system with
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Heitor Alves de
of thcount (they are alias to the same
data, and nlwp works fine in both versions).
** Also affects: procps (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: procps (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: procps (Ubuntu Xenial)
Status
1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
[2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
** Affects: zfs-linux (Debian)
Importance: Unkn
Verified on Bionic with the following test case:
$ echo 64 | sudo tee /sys/class/net/ens1f0/device/sriov_numvfs && virsh
attach-interface valuable-bluefish hostdev :08:02.6 --managed --live
On 4.15.0-72.81, I get the following GPF:
[119044.656412] general protection fault: [#1] SMP PTI
[
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
** Also affects: zfs-linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
** Patch added: "lp1856084-eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+attachment/5312045/+files/lp1856084-eoan.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Tags added: sts-sponsor
** Patch added: "lp1856084-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+attachment/5312043/+files/lp1856084-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Patch added: "lp1856084-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+attachment/5312044/+files/lp1856084-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Verified on disco with the following test case:
$ uname -r
5.0.0-38-generic
$ echo 64 | sudo tee /sys/class/net/ens1f0/device/sriov_numvfs && virsh
attach-interface iov hostdev :08:02.6 --managed --live
64
Interface attached successfully
** Tags removed: verification-needed-disco
** Tags add
** Patch added: "lp1856084-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+attachment/5312221/+files/lp1856084-focal.debdiff
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
cided
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags: sts
** Changed in: linux (Ubuntu)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
When mounting LVM snapshots using xfs, it's possible to hit a BUG_ON() in
nvme driver.
Upstream commit 729204ef49ec ("block: relax check on sg gap") introduced
a way to merge bios if they are physically contiguous. This can lead to
issues if one rq st
Patches sent out to kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2020-March/108551.html
https://lists.ubuntu.com/archives/kernel-team/2020-March/108552.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
For reference, the kernel spew of the BUG_ON:
[ 78.354129] kernel BUG at
/home/ubuntu/xenial-aws/drivers/nvme/host/pci.c:619!
[ 78.357297] invalid opcode: [#1] SMP
[ 78.359613] Modules linked in: dm_snapshot dm_bufio xfs ppdev serio_raw
parport_pc 8250_fintek parport i2c_piix4 ib_iser
Verified according to test case from description:
ubuntu@xenial:~$ dpkg -l | grep procps
ii procps 2:3.3.10-4ubuntu2.5
amd64/proc file system utilities
ubuntu@xenial:~$ ps -o thcount
THCNT
1
1
** Tags removed: verification-needed
The cond_resched() patch should make its way into the 5.4 merge window
(see bcache maintainer's reponse at [0]).
[0] https://lore.kernel.org/lkml/74950e24-245a-c627-0e2e-
32ac0b304...@suse.de/
** Also affects: linux
Importance: Undecided
Status: New
** Changed in: linux
Status:
Assignee: Heitor Alves de Siqueira (halves)
Status: New
** Affects: systemd (Ubuntu Xenial)
Importance: Undecided
Assignee: Heitor Alves de Siqueira (halves)
Status: New
** Tags: sts
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Also
** Changed in: dbus (Ubuntu Xenial)
Status: New => In Progress
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-l
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connect
** Patch added: "lp1846787-systemd-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1846787/+attachment/5295137/+files/lp1846787-systemd-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connect
Validated debconf from disco-proposed according to test case from
description:
root@disco:~# dpkg -l | grep debconf
ii debconf 1.5.71ubuntu1 all
Debian configuration management system
root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc
Validated debconf from cosmic-proposed according to test case from
description:
root@cosmic:~# dpkg -l | grep debconf
ii debconf 1.5.69ubuntu1 all
Debian configuration management system
root@cosmic:~# run-parts --exit-on-error --arg=5.0.0 /
I've checked the other daemons in resource-agents, and it doesn't seem
like removing the /var/lock/subsys stuff will cause any issues. Quick
tests on a disco container showed that it fixes the problem as well.
I submitted a PR upstream to engage the devs on a discussion about those
locks: https://
Validated debconf from bionic-proposed according to test case from
description:
root@bionic:~# dpkg -l | grep debconf
ii debconf 1.5.66ubuntu1
all Debian configuration management system
root@bionic:~# run-parts --exit-on-error --arg
Validated debconf from xenial-proposed according to test case from
description:
root@xenial:~# dpkg -l | grep debconf
ii debconf 1.5.58ubuntu2
all Debian configuration management system
root@xenial:~# run-parts --exit-on-error --arg
Some comments on the autopkgtest regressions:
# Disco
- prometheus-blackbox-exporter and open-isns fail due to package dependency
problems, unrelated to debconf
- makedumpfile fails with "sudo: /tmp/autopkgtest-run-wrapper: command
not found", which has happened in other previous autopkgtests
(p
Verified resource-agents from xenial-proposed according to test case
from description:
root@xenial:~# dpkg -l | grep resource-agents
ii resource-agents 1:3.9.7-1ubuntu1.1
amd64Cluster Resource Agents
root@xenial:~# ip addr show dev virbr0-nic
3:
Verified resource-agents from cosmic-proposed according to test case
from description. The WARNING messages about monitoring failure are
fine, as long as we don't get "WARNING: Interface virbr0-nic does not
exist".
root@cosmic:~# dpkg -l | grep resource-agents
ii resource-agents 1
Verified resource-agents from bionic-proposed according to test case
from description. The WARNING messages about monitoring failure are
fine, as long as we don't get "WARNING: Interface virbr0-nic does not
exist".
root@bionic:~# dpkg -l | grep resource-agents
ii resource-agents 1
* Changed in: pcs (Ubuntu Disco)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826045
Title:
Unsatisfiable
# NOTE
Due to bug 1826045, I've done the test below with a patched version of pcs to
work around the pacemaker/pcs version problems. The pcs package does not affect
the resource-agents SRU, and is only used for an easy, straightforward
reproducer.
#
Verified resource-agents from disco-proposed
Quick note on the autopkgtest regression for resource-agents:
that autopkgtest fails due to bug 1828258, which causes a package
configuration from dpkg to fail (and consequently, the test). It's not
related to this SRU, and the rest of the autopkgtest log looks fine.
** Tags removed: verification
** Description changed:
- The current version of pcs in disco is 0.10.x, which requires pacemaker
- >= 2.0 and corosync >=3.0, neither of which are available yet. Should
- the version be downgraded to 0.9.x until the other packages are updated?
+ [Impact]
+ pcs can't be used for pacemaker and coro
{1..10}; do taskset 0x10 cat
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done
3) Monitor the read/write workload for any performance impact
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Heitor Alves de Siqueira (halves)
Status: New
** Tags: s
This has been reported upstream as well, with a tentative patch in
https://lkml.org/lkml/2019/3/7/8
I've done some tests in fio to get some more data on this issue, with the
following scenarios:
- "raw" test -> fio test without any sysfs queries
- "sysfs" test -> fio + scripted sysfs querie
>From the comparison graphs, we can see that the impact of the sysfs
query is very significant for both read and write workloads. Taking just
the "sysfs" test from my previous comment into account:
In the random write tests:
* For 512b block sizes, we see about an 85% reduction in BW (down to ~2MB
I've uploaded comparison graphs at [0] to avoid decompressing the
.tar.gz archive. Complete logs and graphs from individual runs are in
the archive only, as they're too unwieldy to navigate.
[0] https://people.canonical.com/~halves/priority_stats/
--
You received this bug notification because yo
Verified fix for Xenial:
ubuntu@xenial:~$ systemctl reboot
Operation inhibited by "APT" (PID 1311 "apt", user root), reason is "APT is
installing or removing packages".
Please retry operation after closing inhibitors and logging out other users.
Alternatively, ignore inhibitors and users with 'sy
Some notes for reference:
We might actually have some trouble in expressing the Lifetime of an
Address in the Netplan schema. From the Netplan Reference [0] we can see
that the 'addresses:' field accepts a list of mixed IPv4 and IPv6
addresses. We can't just add a 'lifetime:' field to the schema,
Even in the case that you are operating on a remote server, the remote
pcsd client needs pacemaker/corosync scripts. Without that, even the
very basic commands won't work:
ubuntu@disco:~$ pcs status
Error: unable to run command crm_mon --one-shot --inactive: No such file or
directory: 'crm_mon'
u
1 - 100 of 387 matches
Mail list logo
