Observed in B/aws (kernel 4.15), cycle sru-20210621.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because
Observed in B/aws (kernel 4.15), cycle sru-20210621.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because
Observed this on B/oracle-5.4, cycle sru-20210621 .
** Tags added: oracle
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Also affects: lxc
Importance: Undecided
Status: New
** No longer affects: lxc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc
Observed on B/aws-5.4 , cycle 20210621.
** Tags added: 5.4 aws bionic sru-20210621
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc 3.0.3-0ubuntu1~18.04.1
Observed in B/aws-5.4, cycle sru-20210621.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because systemd
** Summary changed:
- lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
+ lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
(device_add_remove_test)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1886790 ***
https://bugs.launchpad.net/bugs/1886790
** This bug has been marked a duplicate of bug 1886790
lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
--
You received this bug notification because you are a member of Ubuntu
Found on B-5.4/aws, cycle sru-20210531 .
** Tags added: sru-20210531
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 /
Observed with B-5.4/aws, cycle sru-20210531 .
** Tags added: sru-20210531
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove from
Issue observed for a long time in 5.8 kernels, for example G/KVM.
** Tags added: 5.8 groovy kvm sru-20210531
** Tags added: sru-20210510
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Marked https://bugs.launchpad.net/bugs/1900662 as duplicate of this one.
Same issue, and seems (per Christian) that is fixed on 4.0.6 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome
Oh, so it's explained! Thanks Javier for the data. You're using an
outdated version of the package that doesn't contain this fix. You need
initramfs-tools version 0.122ubuntu8.17 - you can either try to get an
updated cloud image, or after the first boot you may be able to update
it (you could
Thanks for the report Javier! What version of initramfs-tools are you
using ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
Cloud images fail to
John, thanks a lot for your report! Definitely we don't want to delay boots -
although I'm happy to hear that eventually it boots. Can you send me logs so I
can understand what's going on?
My suggestion is to follow the steps below (as root user):
(0) [optional] Force a log rotation, in order
I was able to verify this bug with systemd from bionic-proposed (version
237-3ubuntu10.43) by following the procedure in the test case; it's
working as expected, I can see 64M in the memlock limit.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
Thanks for releasing the packages in -proposed Lukasz. I was able to
complete the validation for the Focal version, following the procedure
in the description. An user reported internally to me that the
verification of Bionic version was also successful, hence I'm hereby
marking this LP as
ols (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherm
Thanks a lot Alex for your review from a security point-of-view. And thanks
again Lukasz for dealing with this SRU!
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Thanks a bunch mfo!!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Status
Hi Eric, all the changes are part of the same functionality - the local-bottom
script for example is a clean-up for the files created in the local-top phase.
I think it'd be unnecessary verbosity to explain file by file, and this bug is
waiting for a long time to be fixed (especially due to the
** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411486/+files/bionic_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "focal_cryptsetup_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5411485/+files/focal_cryptsetup_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
After the cryptsetup FTBFS investigation (on LP #1891473), coincidentally a
security fix was released for such package, that included a fix for the FTBFS.
So, this is a "rebase" on top of the latest version for Focal/Groovy - Bionic
wasn't affected, but I'm re-uploading its debdiff
** Patch added: "This is the (tested) debdiff with the proposed SRU, for Bionic
only."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+attachment/5409870/+files/bionic_systemd_lp1830746.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
e/ubuntu/test1830746
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Focal)
ystemd (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided =>
I've managed to verify the initramfs-tools Focal-proposed package
(version 0.136ubuntu6.3) by following 2 approaches, given that we don't
have its cryptsetup counter-part released yet:
(a) The verification by "negation" aims to check if we don't have
regression, by testing if the new package
I've tested the Focal-proposed initramfs-tools (version 0.136ubuntu6.3 )
according to the "Test Case" section in the description, and it's working as
expected. Also, the armhf autopkgtest failure is no longer an issue (test was
re-executed with success), so marking as verified!
Cheers,
The ARMHF testing was retried (thanks mfo!) and passed, likely flaky
network issues during the test. Also, since Focal was successful to
build and no issues on autopkgtest were reported (i.e., no test fails
detected), I'm hereby marking this as verified.
Cheers,
Guilherme
** Tags removed:
After discussing with Eric, seems initramfs-tools was "released" in
Groovy (even with autopkgtest), so I'm hereby attaching an updated
debdiff only with the autopkgtest fix.
** Patch added: "groovy_initramfs_lp1879980_lp1893675_V3.debdiff"
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5406228/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly
Worth to notice that the cryptsetup release is blocked on LP #1891473 -
there's a failure on building this package from source introduced by a
recent PPA builder upgrade (from Xenial to Bionic).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5406230/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP
#1893675) - it's non-related with the fixes proposed here, but we need to make
autopkgtest happy or we cannot get the package released, so here goes the V2 of
the initramfs-tools debdiffs.
Notice the SRU is mainly
Although the debdiffs are being hereby attached, the SRU track is
ongoing in LPs #1879987 and #1879980.
** Patch added: "groovy_initramfs_lp1879980_V2.debdiff"
** Patch added: "focal_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406204/+files/focal_initramfs_lp1879980_V2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
[Impact]
* Currently the initramfs-tools autopkgtest fails for at least AMD64, with
the following signature:
"mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device
/dev/loop0p1 does not exist."
* The reason for that is the test trying immediately to
: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Focal)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Groovy)
Importa
test is not executed in Debian CI given that CI has
no support for VMs, and this test requires that.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: seg
--
You received this bug notification beca
After about 10 weeks, finally my patch was merged by the Debian
maintainer: https://salsa.debian.org/kernel-team/initramfs-
tools/-/commit/c3cbf355
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5401090/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You received
Attaching a new Bionic debdiff, which now includes a fix for a third bug
(LP #1820929).
** Patch added: "bionic_initramfs_lp1879980_V2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5401089/+files/bionic_initramfs_lp1879980_V2.debdiff
--
You
Although the debdiff is hereby attached, 3 bugs have fixes carried on
such patch - the main work is done on LP ##1879980 (and the other LP
handled in this SRU is #1879987) .
** Tags added: sts
** Description changed:
- This bug is a follow-up to
+ [Impact]
-
signed) => Guilherme G. Piccoli (gpiccoli)
** Changed in: initramfs-tools (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Jay Vosburgh (jvosburgh)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ini
Just got a test result from an user that reported the issue - the packages with
the proposed patches [0] fixed the issue to him.
cheers,
Guilherme
[0] https://launchpad.net/~gpiccoli/+archive/ubuntu/lp1879980
--
You received this bug notification because you are a member of Ubuntu
Touch
** Patch added: "focal_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398703/+files/focal_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "xenial_initramfs_lp1879987.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398705/+files/xenial_initramfs_lp1879987.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Worth to notice that the debdiffs (except Xenial's) include a fix for LP
#1879980 - we are doing a single SRU for 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Patch added: "groovy_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398702/+files/groovy_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "bionic_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5398704/+files/bionic_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "focal_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398699/+files/focal_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "groovy_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398696/+files/groovy_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "bionic_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398701/+files/bionic_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "groovy_initramfs_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398697/+files/groovy_initramfs_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "focal_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398698/+files/focal_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Worth to notice that the initramfs-tools debdiffs include a fix for LP
#1879987 - we are doing a single SRU for 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
One relevant discussion would be why we decided to not change mdadm code
anymore. What happens here is that we have an inter-dependency between
mdadm and cryptroot - we first changed the mdadm max counter to
"untangle" that relation, in a way cryptroot would run more times than
mdadm.
But
** Patch added: "bionic_cryptsetup_lp1879980.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5398700/+files/bionic_cryptsetup_lp1879980.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Oh, I forgot to mention - Xenial won't be fixed. It's a release pretty stable
with less then a year remaining of regular support, and with older code. So, in
my opinion (again) it's safer to keep it as is, and consider that degraded
RAID1 + encrypted rootfs is fully supported on Bionic and so
** Description changed:
[Impact]
- * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu
is currently unable to decrypt the rootfs if the array gets degraded, like for
example if one of the array members gets removed.
+ * Considering a setup of a encrypted rootfs on
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Opinion
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => In Progress
** Also affects: mdadm (Ubuntu Groovy)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Opinion
** Also a
** Description changed:
- kernel get stucks at boot if console=ttyS* is specified in the kernel
- cmdline and that serial HW isn't available on the system.
+ [Impact]
- Reproduced with:
- 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
+ * Currently, if
Let me clarify why I'm un-marking this as duplicate of #1573095. This LP
bug is indeed a duplicate of #1573095, but we have a lot of noise there,
and potentially multiple different issues reported. The main one is the
wrong ttySX causing the infinite loop in initramfs-tools due to error on
write.
ded
Status: New
** Also affects: initramfs-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Groovy)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Changed in: initramfs-tools (Ubuntu E
Thanks Roger and Kobus for your report! Do you know if the problem persists on
Xenial (16.04) or later Ubuntu releases? We don't support fixes for Trusty
anymore except for security ones, so I've marked as "won't fix". In case you
can reproduce with newer versions, let us know.
Cheers,
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => In Progress
** Bug watch added: Debian Bug tracker #933059
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933059
** Also affects: cryptsetup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933059
Debian merge request for the cryptsetup patch was just submitted:
https://salsa.debian.org/cryptsetup-team/cryptsetup/-/merge_requests/18
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
** Description changed:
- Description will be saved for further SRU template, the details of the
- issue will be exposed in comments
+ [Impact]
+ * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu
is currently unable to decrypt the rootfs if the array gets degraded,
I have a report of a Bionic user that tested the packages on my PPA with
success.
I changed a small bit though, from the first proposal (just for consistency):
moved the cryptsetup clean-up script to local-bottom instead of init-bottom.
Thanks,
Guilherme
--
You received this bug
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Although this is closed as dup, I thought would be good to clarify why
Debian Buster doesn't reproduce (at first). What happens is that Debian
includes the fsck on initrd by default, and in Ubuntu that
List of somewhat duplicate bugs:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375
(after comment #74)
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/251164
(propose some alternative solutions we can think about, like failure hooks)
Not a debdiff - I found easier to just add the patches as in my local
git repository of the packages.
** Patch added: "cryptroot patch"
** Patch added: "mdadm patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375736/+files/0001-script.local-block-Improve-last-resort-mechanism.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "initramfs-tools patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375735/+files/0001-scripts-local-Allow-local-block-looping-as-Debian.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The issue basically is about a failure in mounting root if we have a
stacked setup of LUKS on top of RAID1, when RAID1 is degraded (like a
member missing). What happens in detail is a conjuncture of factors
leading to this problem:
(a) The initramfs script for cryptroot currently is present in
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Sorry, dup of LP #1573095.
** This bug has been marked a duplicate of bug 1573095
Cloud images fail to boot when a serial port is not available
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Eric, I'll close this LP as dup of #1879987 - seems it's the same issue.
I'll try also the Debian release top see what's different there...we can
comment in the other bug about Debian status and what are
This was greatly debugged by LP user WGH in https://bugs.launchpad.net
/cloud-images/+bug/1573095/comments/46 - it's really a flaw on
initramfs, I managed to workaround the issue with "quiet" parameter
(system boots normally ,even with the wrong serial console).
Investigation continues... I guess
Public bug reported:
Description will be saved for further SRU template, the details of the
issue will be exposed in comments
** Affects: cryptsetup (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: initramfs-tools (Ubuntu
Thanks a lot Eric and Brian for handling the SRU process.
I just tested the packages initramfs-tools and initramfs-tools-bin version
0.103ubuntu4.11, from trusty-proposed, following the test procedure of this
LP's description.
Everything is working fine, so I'll mark this as verification-done.
This solution was suggested by Szilard Cserey and further improved by
Dan Streetman - thanks both!
** Patch added: "lp1771557_v1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771557/+attachment/5140444/+files/lp1771557_v1.debdiff
--
You received this bug
** Description changed:
- [Impact]
- The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to
nvmeXnY block device, so it's failing and not building the initram disk.
+ [Impact]
- Upstream solution is composed for at least 2 patches (it's a series, but
+ When creating the
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Fix Released
** Changed in: initramfs-tools (Ubuntu)
Importance: High => Medium
** Changed in: initramfs-tools (Ubuntu)
Milestone: trusty-updates => None
--
You received this bug notification because you are a member
mportance: Undecided => High
** Changed in: initramfs-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: initramfs-tools (Ubuntu Trusty)
Milestone: None => tr
As mentioned by Dan in the above comments, some failures in autopkgtest
like:
autopkgtest [14:44:48]: test ubuntu-regression-suite: [---
Source Package Version: 4.4.0-1017.17
Running Kernel Version: 3.13.0-145.194
ERROR: running version does not match source package
Are
Thanks a lot for your feedback Marcelo; I'm glad everything seems fine now.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1303649
Title:
systemd-logind
For the folks that observed the recent cgmanager issue with logind:
there's a new systemd version in -proposed; it's version
"204-5ubuntu20.28". I've just tested it with and without cgmanager, in
kernels 4.4.0-119 and 3.13.0-145 (according to LP #1750013), and didn't
observe any constant CPU
Hi Łukasz, thanks for the heads-up.
I just tested systemd from -proposed, version 204-5ubuntu20.28 and it
fixes the issue reported in this LP.
The test consists in doing multiple SSHs in a loop (better explained in
the description). I've run the test with and without cgmanager
installed, in
Dan, this is the v3 of the patch. I bumped the version to 20.28 since my
proposed 20.27 caused the regression aforementioned.
For this version, I removed the dependency of cgmanager, along with the
code that added closing sessions to garbage collector. Happens that a
similar code is present on
Folks that are experiencing this issue: the best way to circumvent it
for now I guess it's downgrade systemd package to version
204-5ubuntu20.26 and remove cgmanager.
To remove cgmanager: "sudo apt-get remove cgmanager"
To downgrade systemd version: "sudo apt-get install systemd-
Thank you Mauro! One thing that worth to take a look is that you're
using kernel 3.13, and this could be related to the high CPU utilization
issue you're observing.
We're changing the approach of this fix to not rely on cgmanager
anymore. The CPU utilization issue is however another bug that
Thanks Dale and Marcelo for your quick report - this is really useful.
The problem seem to be caused due to cgmanager being added as dependency
of systemd in -proposed - this request was clearly explained in LP
#1750013 (not a dup for this, it's another issue with systemd-logind).
During my test
Thanks Stéphane, the 2nd point is a reasonable consideration.
Regardless if I could provide a fix to cgmanager for the regression,
certainly it won't be added again as a dependency.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
We had a potential regression reported after some users installed this package
from -proposed.
The reports starts on comment #17 in LP: #1303649 .
Summary: users are reporting high CPU loads from both systemd-logind and
cgmanager processes, as well as delays in logins. I'm investigating to
Thanks Dan and Brian.
Just tested: after 1h and more than 5500 SSH sessions, no leaks at all were
observed.
(As a comparison, testing the "old" version 20.26 I got 1.8 MB of leak in half
an hour!)
Cheers,
Guilherme
** Tags removed: sts-sru-needed verification-needed
Thanks Dan.
About cgmanager: if we don't have it installed, it does not affect
memory of systemd-logind tool per se. What happens, IMHO, is even more
severe: we don't free/de-allocate sysfs cgroup paths for sessions. So,
in my tests _without_ cgmanager, after 8000 SSH sessions to my target
1 - 100 of 111 matches
Mail list logo
