** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
** Tags added: fr-2124
--
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/1962332
Title:
xenial systemd fails to start if cgroup2 is mounted
Status in systemd package in
It's the SRU team's purview to make exceptions here. The rationale that
this only benefits images is and therefore needs to be in the main
archive is sound. So for the SRU team, I'm +1 on going ahead with this.
But someone still needs to prepare the SRU, which I think falls to
Foundations.
--
I feel like this special case should be decided and handled by the
release team, not Foundations.
--
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/1962332
Title:
xenial
Just for clarification, and doc, this approach was took as since it
needs to go the archive, it need to be handled as an SRU bye the SRU
team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I see, I do agree, sorry for noise. I did remove the one from -esm ppas
and here is the debdiff. Could someone please sponsor/follow with it?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Patch added: "systemd_229-4ubuntu22.32.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+attachment/5569222/+files/systemd_229-4ubuntu22.32.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
+1 to Dan
Having it in ESM is not really helpful (esp. not for package tests).
If it's patched in the regular archives (xenial-updates), I am happy to
re-try and test.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
> I have update ongoing on esm-infa-staging for it
just to clarify, if the systemd patch isn't added to the actual main
(currently closed) xenial-updates repo, it won't be very much help to
anyone wanting to create new xenial containers on jammy. So, just
patching systemd in the esm repo likely
I have update ongoing on esm-infa-staging for it, but without consider
these issues Dimitri pointed, so, with the clean patch pointed here. It
would be nice if any of you folks could give a test on it. Also adding
other folks from security to this discussion with better background.
Also, tips on
Backporting 099619957a0 to xenial will mean that systemd will gain
ability to use cgroups2 as shipped in the xenial's ga v4.4 kernel.
it will mean that xenial containers on top of bionic's ga kernel will
fail to use cgroups2.
however at the time it was an experimental feature which was not
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
hm, $ lxc launch --vm ubuntu:xenial fails for me
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system,
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the
Irrespective of ESM status, we have always had extremely long support
overlaps both backwards and forwards between ubuntu releases.
At the moment, my only solution is to use lxd vms; i.e.
do
$ lxc launch --vm ubuntu:xenial
However, I say for the sake of ease of development, testing, upgrades,
> "so this is fixed already in f and later" - think you mean "b and
later" here?
yes sorry, fixed in b and later
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems
(not reassigning because I'm not sure of a public team that can be used
for ESM bug assignments, but I've contacted the engineering team
internally.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
NB this has been assigned to Canonical Foundations, but as Ubuntu 16.04
is in Extended Security Maintenance now, this is actually a decision for
our ESM Team to make regarding the path forward on whether xenial
containers will be supported on jammy hosts, and if so, to update
systemd for it.
--
"so this is fixed already in f and later" - think you mean "b and later"
here?
--
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/1962332
Title:
xenial systemd fails to start
This bug is a consequence of LP#1962286.
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
21 matches
Mail list logo
