Similar to bug 1888000, it appears this failure has also always been
present. I verified this against the focal 20200423 (oldest release with
5.4.0-1009-kvm) and 20200703 (newest release with 5.4.0-1018-kvm)
serials.
While this is no longer blocking image publication, is this something
that could be fixed in order to prevent us from shipping with failed
systemd units?
Both images produce a failure similar to:
Jul 20 12:15:30 ubuntu systemd[1]: systemd-sysctl.service: Main process exit
ed, code=exited, status=1/FAILURE
Jul 20 12:15:30 ubuntu systemd[1]: systemd-sysctl.service: Faile
d with result 'exit-code'.
Jul 20 12:15:30 ubuntu systemd[1]: Failed to start Apply Kernel Variables.
Jul 20 12:15:30 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to
'kernel/pid_max': Invalid argument
** Description changed:
Overview
---
- This is *blocking* new minimal image promotion. Starting on or around
20200714, the Focal minimal cloud images reported they failed to apply kernel
variables during boot.
-
+ It appears the Focal minimal images have always shipped with a failing
systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304'
to 'kernel/pid_max': Invalid argument"
Expected results
---
$ sudo systemctl list-units --failed --no-legend
# Return no failed units
-
Actual results
---
$ sudo systemctl list-units --failed --no-legend
- systemd-modules-load.service loaded failed failed Load Kernel Modules
+ systemd-sysctl.service loaded failed failed Apply Kernel Variables
+
From the journal:
- Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Main process
exited, code=exited, status=1/FAILURE
- Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Failed with result
'exit-code'.
- Jul 17 10:30:12 ubuntu systemd[1]: Failed to start Apply Kernel Variables.
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '176' to
'kernel/sysrq', ignoring: No such file or directory
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write 'fq_codel' to
'net/core/default_qdisc', ignoring: No such file or directory
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to
'kernel/pid_max': Invalid argument
+ Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit
+ ed, code=exited, status=1/FAILURE
+ Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile
+ d with result 'exit-code'.
+ Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables.
+
+ Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker
+ nel/pid_max': Invalid argument
Steps to reproduce
---
- 1. Download image from:
https://private-fileshare.canonical.com/~powersj/minimal-focal/
- 2. multipass launch file:///
- 3. multipass exec -- sudo systemctl list-units --failed --no-legend
- ---
+ $ wget
https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img
+ $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img
--name=focal-minimal
+ $ multipass exec focal-minimal -- sudo systemctl list-units --failed
--no-legend
+
+
+ ---
ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
-
+
ProcEnviron:
- TERM=xterm
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=C.UTF-8
- SHELL=/bin/bash
+ TERM=xterm
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
ProcFB:
-
+
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm
root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0
ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44
RelatedPackageVersions:
- linux-restricted-modules-5.4.0-1018-kvm N/A
- linux-backports-modules-5.4.0-1018-kvm N/A
- linux-firmware
