During a discussion about the potential for autopkgtests it was brought
up that a representative sample of unfiltered vmcores would be large
(even compressed). This would impose bandwidth and disk space
constraints on anyone attempting to run the autopkgtests locally.
That tends to make me lean
Thanks everyone for the awesome input and ideas! I will draft the
special case exception and figure out some way to post it here for
review.
Regarding testing, I really like Dann and Guilherme's idea for automated
testing of vmcores.
Where would that infrastructure live and how would we maintain
Hi Guilherme!
I have been looking at the possibility of an SRU exception for
makedumpfile, although I like your idea better (LTS N to LTS N+1).
How would we go about implementing that? I am willing to do the
building/testing work, but would need guidance on how to do that and
properly
** Summary changed:
- makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte.
+ makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
** Affects: makedumpfile (Ubuntu)
Importance: Undecided
Assignee: Kellen Renshaw (krenshaw)
Status: New
*
** Attachment added: "109-xfs-bionic.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5584117/+files/109-xfs-bionic.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification for Bionic
Ran the xfstests (https://git.kernel.org/pub/scm/fs/xfs/xfstests-
dev.git) on the current 5.4.0-109-generic #123~18.04.1-Ubuntu kernel and
the -proposed kernel 5.4.0-110-generic #124~18.04.1-Ubuntu in a VM to
exercise the XFS filesystem thoroughly. Detailed log files of
** Attachment added: "110-xfs.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5582132/+files/110-xfs.log
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Verification for Focal
Ran the xfstests (https://git.kernel.org/pub/scm/fs/xfs/xfstests-
dev.git) on the current 5.4.0-109-generic #123-Ubuntu kernel and the
-proposed kernel 5.4.0-110-generic #124-Ubuntu in a VM to exercise the
XFS filesystem thoroughly. Detailed log files of the tests are
Public bug reported:
Observed very infrequent errors (404s squashed to 200s, 201s squashed to
200s) when connection reuse was enabled in mod_proxy_http on Ubuntu
Focal.
The squashing occurs because the corrupted status line is read as a
HTTP/0.9 response by mod_proxy_http, which has only the 200
Unable to run the apport command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966803
Title:
xfs: Fix deadlock between AGI
Example backtraces:
Mar 4 05:41:40 host kernel: [291932.968664] INFO: task tar:44877 blocked for
more than 120 seconds.
Mar 4 05:41:40 host kernel: [291932.968826] Tainted: P OE
5.4.0-100-generic #113~18.04.1-Ubuntu
Mar 4 05:41:40 host kernel: [291932.969019] "echo 0 >
Public bug reported:
SRU Justification:
[Impact]
* The xfs filesystem suffers from a deadlock issue in kernels < 5.5.
This hangs IO to/from the affected filesystem.
[Fix]
* 93597ae8dac0149b5c00b787cba6bf7ba213e666 93597ae8dac0 "xfs: Fix
deadlock between AGI and AGF when target_ip exists in
Bionic verification
root@verify-lp1953610-bionic:~# ### Verification
root@verify-lp1953610-bionic:~# # Install updated command-not-found from
-proposed
root@verify-lp1953610-bionic:~# # https://wiki.ubuntu.com/Testing/EnableProposed
root@verify-lp1953610-bionic:~# cat
Focal verification
root@verify-lp1953610-focal:~# ### Verification
root@verify-lp1953610-focal:~# # Install updated command-not-found from
-proposed
root@verify-lp1953610-focal:~# # https://wiki.ubuntu.com/Testing/EnableProposed
root@verify-lp1953610-focal:~# # Update command-not-found.
Verification for Impish
root@verify-lp1953610-impish:~# ### Verification
# Install updated command-not-found from -proposed
# https://wiki.ubuntu.com/Testing/EnableProposed
cat
** Description changed:
[Impact]
- If a non-default umask is set for the root user, then the database created by
cnf-update-db is not readable by users.
+ If a non-default umask is set for the root user, then the database created by
cnf-update-db is not readable by users. This causes
MR for Bionic:
https://code.launchpad.net/~krenshaw/ubuntu/+source/command-not-found/+git/command-not-found/+merge/415622
Testing info attached, uses
https://launchpad.net/~krenshaw/+archive/ubuntu/lp1953610 to provide
packages from the MR.
** Attachment added: "bionic_verify.txt"
Bionic is affected if the system is configured with a non-default
repository that provides CNF metadata. The same fix works for Bionic in
this situation as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1953610
Title:
cnf-update-db creates unreadable database if wrong umask
To manage notifications about this bug go to:
MR for Impish:
https://code.launchpad.net/~krenshaw/ubuntu/+source/command-not-found/+git/command-not-found/+merge/414979
Testing info attached.
** Attachment added: "impish_verify.txt"
MR for Focal:
https://code.launchpad.net/~krenshaw/ubuntu/+source/command-not-found/+git/command-not-found/+merge/414978
NOTE: the Focal packages in the PPA have a version ending in ubuntu2,
this version is identical to the MR's version ubuntu1. Version was
changed to allow PPA building of
The command-not-found-data package in Bionic appears to avoid this
issue, since the script affected by the UMASK variable is not used to
update the databases.
Perhaps this bug doesn't apply to Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[Test Plan]
To reproduce the issue, use the annotated steps below. Confirmed working as a
reproducer for Focal and Impish. Bionic appears to use a -data package instead
of building the db on "apt update"
Notes:
1) The "ubuntu" user below is unprivileged, the result of the "adduser ubuntu"
*** This bug is a duplicate of bug 1953610 ***
https://bugs.launchpad.net/bugs/1953610
** This bug has been marked a duplicate of bug 1953610
cnf-update-db creates unreadable database if wrong umask
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Received this explanation:
CVE-2020-25717 is about samba performing a fallback from "DOMAIN\account" to
simply "account" and ignoring the domain part. This would allow users to take
advantage of the fallback to escalate privileges.
The only way to fix the issue is to remove the fallback, hence
@dbungert Apologies, got sidetracked and this version has been
superceded. Can we rebase this debdiff on the 12.2.13-0ubuntu0.18.04.10
version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840348
Public bug reported:
The patches for CVE-2020-25717 appear to have introduced a functional
regression in the Samba packages 2:4.7.6+dfsg~ubuntu-0ubuntu2.26 and
greater.
After update (both to .26 and .27), the smbd service fails to authenticate
users with the following message:
[2021/12/16
** Changed in: command-not-found (Ubuntu)
Assignee: (unassigned) => Kellen Renshaw (krenshaw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951108
Title:
cnf db mode gets reset based on r
a regression.
** Changed in: cloud-archive/stein
Status: In Progress => Won't Fix
** Changed in: ceph (Ubuntu Bionic)
Assignee: Dan Hill (hillpd) => Kellen Renshaw (krenshaw)
** Changed in: cloud-archive/queens
Assignee: Dan Hill (hillpd) => Kellen Renshaw (krenshaw)
--
You
Public bug reported:
Opening to track upstream issue https://tracker.ceph.com/issues/52804
Issue is HybridAllocator tail latency observed in clusters with NVMe
OSDs after upgrade to Octopus from Mimic.
The allocator default was switched to "hybrid" from "bitmap" by
upstream. Switching the OSDs
Autopkgtest for the attached debdiff.
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+attachment/5523941/+files/log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Proposed debdiff for Focal
** Patch added: "lp1917148_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+attachment/5523939/+files/lp1917148_focal.debdiff
** Description changed:
[Impact]
- * Breakage of tools expecting the version number or the number to
** Description changed:
[Impact]
+ * Breakage of tools expecting the version number or the number to
substantially
+match the Debian package version.
+ * May confuse users expecting the version to substantially match the Debian
+package version.
+ * Restores behavior to that
** Changed in: procps (Ubuntu)
Assignee: (unassigned) => Kellen Renshaw (krenshaw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3
My customized (via 40_custom) grub.cfg that displays the values of
initrdfail (amongst others).
** Attachment added: "grub.cfg"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1901633/+attachment/5427642/+files/grub.cfg
--
You received this bug notification because you are a member of
Public bug reported:
It appears that GRUB in focal (2.04-1ubuntu26.6) doesn't load or save
values to grubenv when using entries that are under a submenu. This is
similar to LP #1816633
For context, this issue arose using the latest focal cloud image (https
SRU Verification, Eoan/19.10
Update, forgot to enable swapaccount=1, corrected verification below
LXD deb in Eoan uses the snap, which includes it's own version of LXCFS.
Testing altered to verify that LXCFS in Eoan/universe is fixed.
root@test-lxcfs-eoan:~# dpkg -l lxcfs
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:2097148 kB
SwapFree:
SRU Verification, Eoan/19.10
LXD deb in Eoan uses the snap, which includes it's own version of LXCFS.
Testing altered to verify that LXCFS in Eoan/universe is fixed.
root@test-lxcfs-eoan:~# dpkg -l lxcfs
Desired=Unknown/Install/Remove/Purge/Hold
|
SRU Verification, Bionic/18.04
ubuntu@lxcfs-test-bionic:~$ dpkg -l | grep lxcfs
ii lxcfs 3.0.3-0ubuntu1~18.04.2
amd64FUSE based filesystem for LXC
ubuntu@lxcfs-test-bionic:~$ lxc launch ubuntu:b sru-test-bionic
To start your first
Test for 19.10/eoan
Autopkgtests:
autopkgtest [16:38:08]: test exercise: ---]
autopkgtest [16:38:08]: test exercise: - - - - - - - - - - results - - - - - -
- - - -
exercise PASS
autopkgtest [16:38:08]: summary
exercise PASS
Revised debdiff, test information for 18.04/bionic
Autopkgtest:
autopkgtest [16:25:54]: test exercise: ---]
autopkgtest [16:25:54]: test exercise: - - - - - - - - - - results - - - - - -
- - - -
exercise PASS
autopkgtest [16:25:54]: summary
New => In Progress
** Changed in: lxcfs (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: lxcfs (Ubuntu Eoan)
Assignee: (unassigned) => Kellen Renshaw (krenshaw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Attaching debdiff
** Patch added: "lp1860813_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1860813/+attachment/5342354/+files/lp1860813_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test for 18.04/bionic
Autopkgtests:
autopkgtest [21:29:26]: test exercise: ---]
autopkgtest [21:29:27]: test exercise: - - - - - - - - - - results - - - - - -
- - - -
exercise PASS
autopkgtest [21:29:27]: summary
exercise PASS
** Changed in: lxcfs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860813
Title:
LXC container reports spike in swap occasionally
To manage
** Changed in: lxcfs (Ubuntu)
Status: Fix Released => New
** Changed in: lxcfs (Ubuntu)
Assignee: (unassigned) => Kellen Renshaw (krenshaw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Previous description, for context:
lxcfs provides a container-specific view of /proc/meminfo. Occasionally, with
near zero or zero swap usage *and* swap accounting turned on (kernel parameter
swapaccount=1), the container will report 100% swap utilization.
Example from Ubuntu 18.04 and lxcfs
Proposed fix: https://github.com/lxc/lxcfs/pull/316
Tested on Ubuntu 18.04 by replacing the lxcfs binary and library, and
retrying the reproducer there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
lxcfs provides a container-specific view of /proc/meminfo. Occasionally,
with near zero or zero swap usage *and* swap accounting turned on
(kernel parameter swapaccount=1), the container will report 100% swap
utilization.
Example from Ubuntu 18.04 and lxcfs
It appears that there is an existing backport:
https://tracker.ceph.com/issues/38714
that depends on:
https://tracker.ceph.com/issues/23223
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843085
Public bug reported:
This issue in the Ceph tracker has been encountered repeatedly with significant
adverse effects on Ceph 12.2.11/12 in Bionic:
https://tracker.ceph.com/issues/38454
This PR is the likely candidate for backporting to correct the issue:
https://github.com/ceph/ceph/pull/26601
Public bug reported:
Upgrading from 12.2.11-0ubuntu0.18.04.2 to 12.2.12-0ubuntu0.18.04.1 on
Ubuntu 18.04 causes the ceph-osd services to be restarted without
prompting.
This appears to be in the configure section on the ceph-common,postinst:
# Automatically added by
Public bug reported:
Multiple incidents have been seen where ops were blocked for various
reasons and the suicide_grace timeout was not observed, meaning that the
OSD failed to suicide as expected.
** Affects: ceph (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Attachment added: "squashfs"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272424/+files/squashfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in
** Attachment added: "vm2_console.log"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272423/+files/vm2_console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
** Attachment added: "vm1_console.log"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272421/+files/vm1_console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
** Attachment added: "host1_dpkg.txt"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272418/+files/host1_dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
** Attachment added: "vm2.xml"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272422/+files/vm2.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in
** Attachment added: "boot-kernel"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272417/+files/boot-kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a
** Attachment added: "host2_dpkg.txt"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272419/+files/host2_dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Ran into this today, attaching the information requested in #51.
Unable to commission/install 18.04 with "No minimum kernel"
MAAS version: maas 2.5.3-7533-g65952b418-0ubuntu1~18.04.1 all
Guests kernel paniced on two hosts (host1 and host2), dpkg -l attached for each
host.
Console output from
** Attachment added: "vm1.xml"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272420/+files/vm1.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a VM in
** Attachment added: "boot-initrd"
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272416/+files/boot-initrd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581
Title:
Composing a
Public bug reported:
Bionic's radosgw package (Version 12.2.11-0ubuntu0.18.04.1 ) can't run
on Bionic, because the version of civetweb in Luminous is incompatible
with libssl1.1, but it's built against libssl1.1.
This has been known about upstream for a while now, and as noted in the
bug-tracker
Public bug reported:
krenshaw@computer:~$ sudo apt purge docker.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
cgroupfs-mount pigz ubuntu-fan
Use 'sudo apt
Hello,
Ran into this bug with iscsitarget 1.4.20.3+svn499-0ubuntu2.3, DKMS
failed to build.
The module built successfully with:
root@fleet-bunny:~# dpkg -l | grep iscsitarget-dkms
ii iscsitarget-dkms 1.4.20.3+svn499-0ubuntu2.5
root@fleet-bunny:~# dkms status
iscsitarget,
Hello Andreas,
Currently, I suspect that it was removed (on purpose or not) manually.
My default client.conf contains it. I will attempt to get more
information on how/why that change was made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Tested on 14.04.5, landscape-client (14.12-0ubuntu6.14.04).
If the data_path directive is not present in /etc/landscape/client.conf, the
postinst script will fail with the following error:
Setting up landscape-client (14.12-0ubuntu6.14.04) ...
install: missing file operand
This bug has been encountered when running Ubiquity with the automatic-
ubiquity kernel option in 16.04. The output of systemctl status
ubiquity.service has the following:
systemd[1]: Starting Ubuntu live CD installer...
start-ubiquity-dm[]: debconf: DbDriver "templatedb":
71 matches
Mail list logo
