Hi Seth,
Thanks for the review.
I read the commit you found:
commit 1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
Author: Dr. David von Oheimb
Date: Sat Jun 27 16:16:12 2020 +0200
Subject: Extend X509 cert checks and error reporting in v3_{purp,crld}.c and
x509_{set,vfy}.c
Link:
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926254
Title:
x509 Certificate verification fails when
basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs
To
Attached is a debdiff for openssl on Groovy which fixes this bug.
** Patch added: "Debdiff for openssl on Groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493443/+files/lp1926254_groovy.debdiff
--
You received this bug notification because you are a member
Attached is a debdiff for openssl on Focal which fixes this bug.
** Patch added: "Debdiff for openssl on focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493442/+files/lp1926254_focal.debdiff
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Groovy)
Assignee: Sinclair Willis (yousure1222) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to
** Description changed:
[Impact]
In openssl 1.1.1f, the below commit was merged:
commit ba4356ae4002a04e28642da60c551877eea804f7
Author: Bernd Edlinger
Date: Sat Jan 4 15:54:53 2020 +0100
Subject: Fix error handling in x509v3_cache_extensions and related functions
Link:
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: openssl (Ubuntu Groovy)
Importance: Medium
Assignee:
@dannf: Yes, this bug sure is a tricky one.
Most of these reports will be due to failing / faulty / non-spec
complaint USB devices or cables, like the original reason for this bug
being opened. Although, there have been some reports where user's
systems do go back to working when they install my
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
Hi Kjell,
Thanks for reporting the issue! We have been tracking it in bug 1923670.
We found the root cause, and we have commit a fix to the source code
tree. This will be fixed in the next kernel update
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it
and confirming it fixes the problem.
Okay, so the problem is:
commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b
Author: Shyam Prasad N
Date: Thu Feb 11 03:26:54 2021 -0800
Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag
Hi @Hmpf,
Thanks for filing a bug report.
I had a look at the changes between 5.4.0-70-generic and
5.4.0-71-generic, and I found three patches for CIFS:
$ git log --grep "cifs" Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
https://paste.ubuntu.com/p/YgrZcN8B6j/
I had a read of the patches, and I
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
** 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/1921104
Title:
net/mlx5e: Add missing capability check for uplink follow
To manage notifications about this bug go to:
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
Performing verification for Focal.
I installed qemu 4.2-3ubuntu6.14 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt
Performing verification for Groovy.
I installed qemu 5.0-5ubuntu9.6 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in gnome-terminal launched from
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added:
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment
Thanks for the quick work Christian!
I'll keep an eye out and be ready to test once builds enter -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921665
Title:
QEMU hits assertion when
Attached is a debdiff for Groovy which fixes this bug.
** Patch added: "QEMU debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481777/+files/lp1921665_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "QEMU debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481776/+files/lp1921665_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
O_DIRECT with NFS
Link:
https://git.qemu.org/?p=qemu.git;a=commit;h=5edc85571e7b7269dce408735eba7507f18ac666
Mailing list discussion:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg721982.html
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affe
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for gnome-shell in Focal.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for Bind9 on Focal.
I first installed 9.16.1-0ubuntu2.6 from -updates to ensure that the
issue is still present.
I checked that I could look up ubuntu.com through the local caching
resolver. From there I started a second VM, and checked I could look up
addresses through
Hi Thimo,
Recently, Xiao Ni, the original author of the Raid10 block discard
patchset, has posted a new revision of the patchset to the linux-raid
mailing list for feedback.
Xiao has fixed the two bugs that caused the regression. The first was
incorrectly calculating the start offset for block
Hi everyone,
The original patch author, Xiao Ni, has sent a V2 patchset to the linux-
raid mailing list for feedback. This new patchset fixes the problems the
previous version had, namely, properly calculating the discard offset
for second and onward disks, and correctly calculates the stripe
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge
Performing verification for Focal.
The affected user enabled -proposed and installed 5.4.0-66-generic to
the system with a QLogic FastLinQ QL41000 Series 10/25/40/50GbE
Controller.
They then set all interfaces down, and brought up the QLogic NIC only.
# uname -rv
5.4.0-66-generic
Performing verification for Focal.
I installed 5.4.0-65-generic to a c5.metal AWS machine, and installed
ubuntu-desktop and a KVM stack. I install xrdp and verified I could
reach the VMs desktop.
I installed virt-manager, and configured the Windows 2k19 VM in
accordance with the testcase
Attached is reproducing the problem with 5.4.0-66-generic. Note that CPU
is low, and system boots to desktop correctly.
** Attachment added: "5.4.0-66-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911848/+attachment/5462097/+files/5.4.0-66-generic.png
--
You received this
Attached is reproducing the problem with 5.4.0-65-generic, note, see how
CPU reaches 100% and is stuck.
** Attachment added: "5.4.0-65-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911848/+attachment/5462096/+files/5.4.0-65-generic.png
--
You received this bug notification
Attached is a V2 of the patch that fixes this bug, Bind9 for Focal.
** Patch removed: "Debdiff for bind9 on Focal"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff
** Patch added: "Debdiff for bind9 on Focal V2"
Attached is a debdiff for Bind9 on Focal to fix this bug.
** Patch added: "Debdiff for bind9 on Focal"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- TCP connections never close
+ named: TCP connections sometimes never close due to race in socket teardown
** Description changed:
- The default timeout for TCP connections on port 53 to named/bind9 is 300
- seconds. The upstream ISC build of bind9 uses this and honors an
-
stuck in ESTABLISHED and not torn down.
I will let you know once there is a new build in -proposed for
verification.
Thanks,
Matthew
** Changed in: bind9 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: bind9 (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mr
Hi Manish,
Thanks for testing the Groovy 5.8 kernel in -proposed!
The Focal 5.4 / Bionic 5.4 HWE kernel will be in -proposed next week
sometime, if you are looking to verify that as well.
I will also ask our customer in common to verify the Bionic HWE kernel
when it becomes available.
Thanks
Hi Adam,
I think I have found the issue that you are experiencing. I don't have a
way to reproduce just yet, but I have built a test package for you to
try.
I came across the following upstream bug:
https://gitlab.isc.org/isc-projects/bind9/-/issues/1700
The users mention that tcp connections
** Also affects: bind9 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Performing verification for Focal.
I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2
from -updates.
>From there I set up the configuration file, launched a new rsyslog
instance, and used netcat to set 100 packets to the relp port.
https://paste.ubuntu.com/p/HfSDvNJzpX/
Performing verification for Focal.
The previous version in -proposed, 1.5.0-1ubuntu2.20.04.1, failed to
build on riscv64, as can be seen in the below links:
https://launchpad.net/ubuntu/+source/librelp/1.5.0-1ubuntu2.20.04.1
Attached is a debdiff for librelp on Hirsute.
** Patch added: "librelp debdiff for hirsute"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456836/+files/lp1912969_librelp_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Changed in: librelp (Ubuntu Hirsute)
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/1912969
Title:
librelp is FTBFS on riscv64 on Focal
To manage notifications
Hi Mauricio,
I filed bug 1912969 to fix the FTBFS for librelp on focal. Adjusting the
packets down from 50,000 to 10,000 makes the build succeed on riscv64.
I attached two debdiffs, one an incremental patch from
1.5.0-1ubuntu2.20.04.1, and the other a full patch from 1.5.0-1ubuntu2.
Please
Attached is a debdiff from librelp_1.5.0-1ubuntu2 to
librelp_1.5.0-1ubuntu2.20.04.2
** Patch added: "librelp debdiff from -1ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456452/+files/lp1912969_librelp_focal_alternate.debdiff
--
You received this bug
Attached is a debdiff for librelp from librelp_1.5.0-1ubuntu2.20.04.1 to
librelp_1.5.0-1ubuntu2.20.04.2
** Patch added: "librelp debdiff from -1ubuntu2.20.04.1"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456439/+files/lp1912969_librelp_focal.debdiff
--
You
** Description changed:
[Impact]
During the recent SRU for bug 1908473, we found that librelp is FTBFS on
riscv64 on Focal, due to the test cases basic-realistic.sh and tls-
basic-realistic.sh failing during dh_auto_test during package build.
dh_auto_test --no-parallel
make -j1
** Description changed:
[Impact]
During the recent SRU for bug 1908473, we found that librelp is FTBFS on
riscv64 on Focal, due to the test cases basic-realistic.sh and tls-
basic-realistic.sh failing during dh_auto_test during package build.
dh_auto_test --no-parallel
-
Undecided
Status: Fix Released
** Affects: librelp (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Changed in: librelp (Ubuntu)
Status: New => Fix Released
** Also affects: librelp (Ubuntu Fo
Hi Mauricio,
It seems riscv64 passes on Groovy due to tests being skipped on the
riscv64 architecture.
>From Groovy's build log:
https://paste.ubuntu.com/p/NCJPDVSbSW/
If you look at the man page for dh_auto_test it mentions:
If the DEB_BUILD_OPTIONS environment variable contains nocheck, no
Performing verification for Focal
I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2
from -updates.
>From there I set up the configuration file, launched a new rsyslog instance,
>and
used netcat to set 100 packets to the relp port.
https://paste.ubuntu.com/p/jCs9Dy6FYF/
Performing verification for librelp in Groovy.
I installed rsyslog-relp 8.2006.0-2ubuntu1 and librelp 1.5.0-1ubuntu2
from -updates to reproduce:
https://paste.ubuntu.com/p/gtn4rcXc72/
>From there I set up the configuration script, ran a new instance of
rsyslog, and used netcat to open 100
Same one failure on today's rebuild. Strange, since this is the exact
same code as Groovy.
** Attachment added:
"buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.5"
Hi Robie, I agree this probably isn't worth a SRU to Groovy, I just made
the packages available in the odd chance that they might be considered.
I will mark Groovy as won't fix.
Hirsute is what really matters in the end.
** Changed in: rsyslog (Ubuntu Groovy)
Status: In Progress => Won't
Hello,
A another user has reported a very similar issue. They operate bind9
resolvers in both recursive and authoritative configurations, and
occasionally, their servers will stop responding to TCP requests.
UDP still operates as normal, but TCP connections will time out.
named is still
Attached is a patch which changes /var/log/dmesg to 0640 on groovy. It
also contains Steve's recommendation to set the logrotate files to 0640.
** Patch added: "Debdiff for syslog on groovy"
Attached is a patch which changes /var/log/dmesg to 0640 on hirsute. It
also contains Steve's recommendation to set the logrotate files to 0640.
** Patch removed: "Debdiff for rsyslog on hirsute"
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912122
Title:
/var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT
restrictions
To manage notifications
Attached is a debdiff for Groovy to change /var/log/dmesg to 0640.
** Patch added: "Debdiff for syslog on groovy"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454005/+files/lp1912122_groovy.debdiff
--
You received this bug notification because you are a member
Attached is a debdiff for hirsute to set /var/log/dmesg to 0640.
** Patch added: "Debdiff for rsyslog on hirsute"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454004/+files/lp1912122_hirsute.debdiff
--
You received this bug notification because you are a
** 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/1912122
Title:
/var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT
restrictions
To manage notifications about this
** Changed in: rsyslog (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: rsyslog (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
[Impact]
)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: rsyslog (Ubuntu Hirsute)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1911848
[Impact]
On CascadeLake based KVM hosts, Windows Server 2k16 and 2k19 guests will
fail to start once they have enabled the hyper-v role for nested
virtualisation.
The Windows Server guests will get stuck
occur, there are no workarounds. Users would
need to downgrade their kernel while a fix is developed.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Pr
signed) => Matthew Ruffell (mruffell)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1909062
[Impact]
For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000
Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel
to the 5.4 kernel, K
I built 1.9.0-1ubuntu0+lp1910307v20210113b2 in
https://launchpad.net/~mruffell/+archive/ubuntu/lp1910307-test, and
contains the identical code to the debdiff above. It builds successfully
on all supported architectures, which also includes riscv64, which means
the patch we merged in still works
Attached is the revised debdiff between librelp_1.9.0-1.dsc and
librelp_1.9.0-1ubuntu1.dsc
** Patch removed: "Debdiff with the merge from Debian"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449599/+files/librelp_diff_debian.debdiff
** Patch added: "Debdiff
** Description changed:
[Impact]
librelp 1.9.0-1 is available in Debian, and is much newer than what we
carry in Ubuntu 1.5.0-1ubuntu2. This bug tracks the merge to the newer
version.
This bug is needed for the SRU of bug 1908473, which fixes a file
descriptor leak in librelp.
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: Fix
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1909062
[Impact]
For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000
Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel
to the 5.4 kernel, Kubernetes Internal DNS requests
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
To
Note - we no longer need to carry the "python2.diff" patch present in
librelp_1.5.0-1ubuntu2.dsc due to the test system being ported to
python3.
The tests have been changed so that the scripts are executed by a python
interpreter, and not bash, so the shbangs for "/usr/bin/env python" are
now
Attached is the debdiff for librelp for Focal
** Patch added: "Debdiff for librelp on Focal"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449602/+files/librelp_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached is the debdiff for librelp for Groovy
** Patch added: "Debdiff for librelp on Groovy"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449601/+files/librelp_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached is the debdiff from librelp_1.5.0-1ubuntu2.dsc to
librelp_1.9.0-1ubuntu1.dsc
** Patch added: "Debdiff with changes from old ubuntu to new ubuntu"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449600/+files/librelp_diff_ubuntu.debdiff
** Description
Attached is the debdiff from librelp_1.9.0-1.dsc to the new
librelp_1.9.0-1ubuntu1.dsc
** Patch added: "Debdiff with the merge from Debian"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449599/+files/librelp_diff_debian.debdiff
--
You received this bug
(Ubuntu)
Importance: Wishlist
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: librelp (Ubuntu Hirsute)
Importance: Wishlist
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Tags added: sts
** Also affects
** Description changed:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks file
descriptors due to a bug where it does not correctly close sockets, and
instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the
Since we only need to change librelp to fix the problem, we won't SRU
the testcase to Focal's rsyslog, since there is no need to risk a
regression for a testcase, which would effectively be a no-change
rebuild.
The testcase is already present in rsyslog on Groovy and Hirsute,
marking as released.
Thanks Manish! I am building a test kernel now, and I will let you know
once it is ready to test.
If we get good test results, I will submit the patch for SRU to the
Ubuntu kernels once the patch has hit mainline.
** Description changed:
- With QL41xxx and Ubuntu DNS server DNS failures are
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Summary changed:
- Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Tobias for the testing. Good to hear it functions as intended.
Performing verification for Bionic
I installed adcli 0.8.2-1ubuntu1.2 from -proposed, and joined a domain
without using the --use-ldaps flag.
https://paste.ubuntu.com/p/RByVZRPhCK/
Next, I added the firewall rules from the
: fix double free of sendbuf in some cases.
Link:
https://github.com/rsyslog/librelp/commit/4a6ad8637c244fd3a1caeb9a93950826f58e956a
** Affects: librelp (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu)
Imp
Hi Tobias,
If you have a moment, could you please help test the new adcli package
in -proposed? Mainly focusing on testing Bionic, to ensure the
regression has been fixed.
Can you run through some tests with and without the --use-ldaps flag?
You can install the new adcli package in -proposed
To anyone following this bug:
As we get ready to re-release the new adcli package which implements the
--use-ldaps flag, if you are happy to spend a few moments testing the
new package, I would really appreciate it. I really don't want to cause
another regression again.
You can install the new
Performing verification for Bionic
Firstly, I installed adcli and libsasl2-modules-gssapi-mit from
-updates:
adcli 0.8.2-1
libsasl2-modules-gssapi-mit 2.1.27~101-g0780600+dfsg-3ubuntu2.1
>From there, I joined a Active Directory realm:
https://paste.ubuntu.com/p/zJhvpRzktk/
Next, I enabled
Hi @hloeung, these patches are available in 4.15.0-128-generic, and
5.4.0-58-generic.
They are both re-spins of 4.15.0-126-generic and 5.4.0-56-generic,
respectively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Benjamin,
The respun kernel has now landed in -updates, and is version
4.15.0-128-generic.
Please re-schedule the maintenance window for the Launchpad git server,
and re-attempt moving to the fixed kernel.
Thanks,
Matthew
--
You received this bug notification because you are a member of
Performing verification for Focal.
I spun up a m5d.4xlarge instance on AWS, to utilise the 2x 300GB NVMe
drives that support block discard.
I enabled -proposed, and installed the 5.4.0-58-generic kernel.
The following is the repro session running through the full testcase:
Performing verification for Bionic.
I spun up a m5d.4xlarge instance on AWS, to utilise the 2x 300GB NVMe
drives that support block discard.
I enabled -proposed, and installed the 4.15.0-128-generic kernel.
The following is the repro session running through the full testcase:
Hi Markus,
I am deeply sorry for causing the regression. We are aware, and tracking
the issue in bug 1907262.
The kernel team have started an emergency revert and you can expect
fixed kernels to be released in the next day or so.
--
You received this bug notification because you are a member
Hi Thimo,
Firstly, thank you for your bug report, we really, really appreciate it.
You are correct, the recent raid10 patches appear to cause filesystem
corruption on raid10 arrays.
I have spent the day reproducing, and I can confirm that the
4.15.0-126-generic, 5.4.0-56-generic and
** 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 Bionic)
Hi Thimo,
Thank you for the very detailed bug report. I will start investigating this
immediately.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard
301 - 400 of 739 matches
Mail list logo
