** Tags removed: foundations-todo
--
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/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd
This bug was fixed in the package systemd - 245.4-4ubuntu3.18
---
systemd (245.4-4ubuntu3.18) focal; urgency=medium
[ Nick Rosbrook ]
* core: make sure we don't get confused when setting TERM for a tty fd
(LP: #1959475)
File:
** Description changed:
[Impact]
This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.
[Test Plan]
On a Jammy host, do the following:
*
Er, I see the problem in my description now. It's been a while since I
looked at this patch. In any case, the patch is still appropriate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> Eh? That isn't at all what the patch does...
Before the patch, the `getenv("TERM")` call would not happen; now it
does.
While fixing path_compare() may be a better long-term solution, I think
the existing patch is appropriate for this bug/SRU.
--
You received this bug notification because
> The patch expands the case where the TERM variable is inherited from
PID 1 when building an execution environment, e.g. for a container. If
problems were to occur, it would be related to the value of TERM in
environments forked off of PID 1.
Eh? That isn't at all what the patch does...
Anyway,
** Tags added: foundations-todo
--
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/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd
The autopkgtest regressions were all resolved with retries.
I verified this fix as well, using the test plan above to create a focal
container with -proposed enabled:
nr@clean-jammy-amd64:~$ lsb_release -cs
jammy
nr@clean-jammy-amd64:~$ sudo machinectl shell test-container
Connected to machine
I can't make comments about the regressions, however I tested the
systemd (245.4-4ubuntu3.18) package in a focal container and confirm
that solves this bug (connecting from a jammy host).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello renbag, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The commit in question is included in upstream v246+, so only affects
Focal.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
A fix for this issue has been staged in git for the next Focal SRU:
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?id=b10c6853050dde26665caf3b15444d768d2bc498
Thank you @enr0n for providing the merge proposal!
** Changed in: systemd (Ubuntu Focal)
Status: New
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/421860
--
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/1959475
** Description changed:
+ [Impact]
+
+ This bug prevents users on Impish and newer from connecting to Focal
+ systemd containers using `machinectl shell`. This limits users ability
+ to manage containers spawned with systemd-nspawn.
+
+ [Test Plan]
+
+ On a Jammy host, do the following:
+
+ *
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Tags removed: rls-ff-incoming rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: fr-2315
--
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/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd package in
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1959475
Title:
"machinectl shell"
** Tags added: focal
--
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/1959475
Title:
"machinectl shell" connections immediately terminated
Status in systemd package in
** Tags added: rls-ff-incoming rls-jj-incoming
--
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/1959475
Title:
"machinectl shell" connections immediately terminated
Status
Please consider backporting for Focal (20.04) at least. The backport is
trivial and applies cleanly as-is except for patch offsets.
Might be wise to test some other combinations though. For example hosts
without this commit, running nspawn containers with it.
--
You received this bug
Just tested, and can confirm backporting
e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 to focal's systemd fixes the
segfaults when using machinectl shell on a Jammy host trying to start a
shell in a Focal nspawn container.
--
You received this bug notification because you are a member of Ubuntu
Touch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
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.
Sorry, the host was running Ubuntu jammy with systemd 249.9-0ubuntu2.
--
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/1959475
Title:
"machinectl shell" connections
>From the last comments in:
https://github.com/systemd/systemd/issues/22234
the problem is due to an incompatibility of the new versions of systemd with
older ones.
In fact the container was running ubuntu focal, with systemd_245.4-4ubuntu3.15,
and the host was running ubuntu focal with
These are the messages reported by journalctl inside the container:
Jan 29 12:27:53 ns-xxx systemd[153]: Assertion 'a' failed at
src/basic/path-util.c:486, function path_compare(). Aborting.
Jan 29 12:27:53 ns-xxx systemd[1]: container-shell@2.service: Succeeded.
-- Subject: Unit succeeded
--
Sorry, the patch in:
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6
is already applied in systemd 249.9-0ubuntu2, so that is not the
solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
26 matches
Mail list logo
