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 =>
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" conn
** 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
Bugs, which is subscribed to Ubun
** Tags added: fr-2315
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
To manage notifications about this bug go to:
https://bugs.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
To manage notifications about this bug go to:
https://bugs.la
** Tags added: rls-ff-incoming rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
To manage notifications about this
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 notificatio
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
Bugs,
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"m
Sorry, the host was running Ubuntu jammy with systemd 249.9-0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959475
Title:
"machinectl shell" connections immediately terminated
To manage no
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 systemd
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
-- Def
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
Bugs, which is subscribed to Ubuntu.
https:
16 matches
Mail list logo
