** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
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/1942113
Title:
systemd unit test regression in autopkgtest
** Merge proposal unlinked:
https://code.launchpad.net/~chacman/ubuntu/+source/systemd/+git/systemd/+merge/410695
--
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/1942113
** Merge proposal linked:
https://code.launchpad.net/~chacman/ubuntu/+source/systemd/+git/systemd/+merge/410695
--
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/1942113
This bug was fixed in the package systemd - 248.3-1ubuntu7
---
systemd (248.3-1ubuntu7) impish; urgency=medium
* d/tests/tests-in-lxd: suppress the cgroups v2 warning on stderr from
lxd/lxc even more comprehensively until the snapd change required to
do it nicely gets into
Merged upstream and staged in: https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/log/?h=ubuntu-impish
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
We do now have an upstream patch/PR:
https://github.com/systemd/systemd/pull/20705
It's not much different from what was already landed in the systemd
package (skipping the test in this scenario). So we should probably only
stage it for the next systemd upload, after it was merged upstream.
--
** Also affects: glibc via
https://github.com/systemd/systemd/issues/20593
Importance: Unknown
Status: Unknown
** Project changed: glibc => systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Unfortunately, it doesn't seem to be the same bug, but might be similar.
I can still reporduce the issue with the upstream daily-build.
I can reproduce it on an Ubuntu Impish host (kernel 5.11.0-31-generic, systemd
248.3-1ubuntu3), running an Ubuntu Impish container (kernel 5.11.0-31-generic,
Sigh yes it does look like you found amd fixed the same bug. Oh well at
least I learnt some things yesterday.
--
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/1942113
Title:
Just a suggestion, before opening an upstream bug, y'all might want to
test with the latest upstream code, as I think this is fixed already?
You can use this ppa to test with the latest upstream (daily) code if it makes
things easier for you:
So it turns out that if you have security.nesting=true set on the
container, then the systemd in proposed manages to set up a unified
hierarchy and the test fails. This is the difference between the
production test runs and mine.
I filed a bug upstream
Hmm something is off here: I'm pretty sure containers inherit their
cgroups mode from the host, so the default hierarchy changing in the
systemd in the archive shouldn't affect anything. I can reproduce the
failure of this report by adding systemd.unified_cgroup_hierarchy=1 to
the kernel command
So yes, that is what matters. When a system is booted with systemd
248.3-1ubuntu3, it sets up the cgroups in "hybrid" mode. systemd
248.3-1ubuntu5 defaults to "unified" mode but simply upgrading the
package does not redo this setup -- the system remains in hybrid mode.
The test cases that are
The difference I can see between the passing and failing run is that in
the failing run, systemd and glibc are upgraded before the "rebooting
testbed after setup commands that affected boot" and in the passing run
they are upgraded after that step. That doesn't make a lot of sense but
maybe the
Funny thing, though :
https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/arm64/s/systemd/20210830_074606_ed6ee@/log.gz -> tests
triggered by the systemd upload. The mentioned test passed. Even though
the libc version *is the same* (2.34-0ubuntu1 has been pulled to satisfy
15 matches
Mail list logo
