| 2023-10-06 13:19:23 |
Brian Candler |
bug |
|
|
added bug |
| 2023-10-06 13:31:35 |
Brian Candler |
description |
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu systemd-nspawn@jammy-rootfs.service"
--------
░░ A start job for unit systemd-nspawn@jammy-rootfs.service has begun execution.
░░
░░ The job identifier is 3223.
Oct 06 13:13:21 brian-kit systemd-nspawn[36720]: Failed to mount image file system: Value too large for defined data type
Oct 06 13:13:21 brian-kit systemd-nspawn[36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit systemd-nspawn@jammy-rootfs.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Failed with result 'exit-code'.
--------
This appears to be similar to https://github.com/systemd/systemd/issues/20989
If so, a fix was committed in March 2022: https://github.com/systemd/systemd/pull/22774
but maybe that was too late for 22.04? Or this is a different problem?
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Oct 6 13:10:41 2023
InstallationDate: Installed on 2022-11-04 (335 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install) |
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu systemd-nspawn@jammy-rootfs.service"
--------
░░ A start job for unit systemd-nspawn@jammy-rootfs.service has begun execution.
░░
░░ The job identifier is 3223.
Oct 06 13:13:21 brian-kit systemd-nspawn[36720]: Failed to mount image file system: Value too large for defined data type
Oct 06 13:13:21 brian-kit systemd-nspawn[36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit systemd-nspawn@jammy-rootfs.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Failed with result 'exit-code'.
--------
This appears to be similar to https://github.com/systemd/systemd/issues/20989#issuecomment-997024152
If so, a fix was committed in March 2022: https://github.com/systemd/systemd/pull/22774
but maybe that was too late for 22.04? Or this is a different problem?
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Oct 6 13:10:41 2023
InstallationDate: Installed on 2022-11-04 (335 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2023-10-06 13:33:12 |
Brian Candler |
description |
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu systemd-nspawn@jammy-rootfs.service"
--------
░░ A start job for unit systemd-nspawn@jammy-rootfs.service has begun execution.
░░
░░ The job identifier is 3223.
Oct 06 13:13:21 brian-kit systemd-nspawn[36720]: Failed to mount image file system: Value too large for defined data type
Oct 06 13:13:21 brian-kit systemd-nspawn[36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit systemd-nspawn@jammy-rootfs.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Failed with result 'exit-code'.
--------
This appears to be similar to https://github.com/systemd/systemd/issues/20989#issuecomment-997024152
If so, a fix was committed in March 2022: https://github.com/systemd/systemd/pull/22774
but maybe that was too late for 22.04? Or this is a different problem?
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Oct 6 13:10:41 2023
InstallationDate: Installed on 2022-11-04 (335 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install) |
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed because the control process exited with error code.
Here's the relevant output from "journalctl -xeu systemd-nspawn@jammy-rootfs.service"
--------
░░ A start job for unit systemd-nspawn@jammy-rootfs.service has begun execution.
░░
░░ The job identifier is 3223.
Oct 06 13:13:21 brian-kit systemd-nspawn[36720]: Failed to mount image file system: Value too large for defined data type
Oct 06 13:13:21 brian-kit systemd-nspawn[36688]: Short read while reading cgroup mode (0 bytes). The child is most likely dead.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit systemd-nspawn@jammy-rootfs.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 06 13:13:21 brian-kit systemd[1]: systemd-nspawn@jammy-rootfs.service: Failed with result 'exit-code'.
--------
This appears to be similar to https://github.com/systemd/systemd/issues/20989
If so, a fix was committed in March 2022: https://github.com/systemd/systemd/pull/22774
but maybe that was too late for 22.04? Or this is a different problem?
EDIT: the reproducer from https://github.com/systemd/systemd/issues/20989#issuecomment-997024152 also reproduces the problem.
# rm -rf /var/lib/machines/my-container/
# mkdir -p /var/lib/machines/my-container/etc
# cp /etc/os-release /var/lib/machines/my-container/etc/
# systemd-nspawn -U -b -D /var/lib/machines/my-container/
Spawning container my-container on /var/lib/machines/my-container.
Press ^] three times within 1s to kill container.
Selected user namespace base 972619776 and range 65536.
Failed to create directory at /var/lib/machines/my-container/usr: Value too large for defined data type
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Oct 6 13:10:41 2023
InstallationDate: Installed on 2022-11-04 (335 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2023-10-30 14:52:07 |
Nick Rosbrook |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-10-30 14:52:07 |
Nick Rosbrook |
bug task added |
|
systemd (Ubuntu Jammy) |
|
| 2023-10-30 14:52:13 |
Nick Rosbrook |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2023-10-30 14:52:18 |
Nick Rosbrook |
systemd (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2023-10-30 14:52:21 |
Nick Rosbrook |
systemd (Ubuntu Jammy): importance |
Undecided |
Low |
|
| 2023-10-30 15:14:13 |
Nick Rosbrook |
bug watch added |
|
https://github.com/systemd/systemd/issues/20989 |
|
