| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the io.systemd.DynamicUser or io.systemd.Machine files exist,
but nothing is listening on them, the nss-systemd module returns
ECONNREFUSED and systemd-sysusers fails to creat the user/group.
This is problematic when ran by packaging scripts, as the package
assumes that after this has run, the user/group exist and can
be used. adduser does not fail in the same situation.
Change sysusers to print a loud warning but otherwise continue
when NSS returns an error.
|
|
|
|
|
|
|
|
|
|
| |
The previous commit tries to extract a substring from the
extension-release suffix, but that is not right, it's only the
images that need to be versioned and extracted, use the extension-release
suffix as-is. Otherwise if it happens to contain a prefix that
matches the wrong image, it will be taken into account.
Follow-up for 37543971aff79f3a37646ffc2bb5845c9394797b
|
|
|
|
|
| |
There is a regression in the login package, skip the test until
it is fixed. https://bugs.debian.org/1075733
|
|\
| |
| | |
Testsuite tweaks for v256 on suse
|
| | |
|
| |
| |
| |
| |
| | |
On SUSE this function is used to copy symlinks installed in *.wants/
directories.
|
| |
| |
| |
| | |
/etc/systemd/journald.conf.d drop-in dir already exists on SUSE.
|
| |
| |
| |
| | |
Needed for resolving the "localhost" hostname.
|
| |
| |
| |
| |
| |
| | |
Although being far from ideal and the first two test cases have to be run
before the setup phase otherwise they will fail, it still makes the test
suite look much better and easier to read
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Various integration test fixes
|
| | |
| | |
| | |
| | |
| | |
| | | |
On aarch64, SMBIOS is only available when using UEFI, so let's make
sure that the creds test uses UEFI when available so that it can
read creds from SMBIOS when running in a virtual machine.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This test runs in nspawn by default but will still run in qemu when
tests are run unprivileged so make sure we use UEFI if available to
avoid hangs when using the linux firmware.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This test runs in nspawn by default but will still run in qemu when
tests are run unprivileged so make sure we use UEFI if available to
avoid hangs when using the linux firmware.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
On x86 this doesn't matter but on aarch64 we need to make sure UEFI
is used so that /sys/kernel/security/tpm0/binary_bios_measurements
is there which is required for TEST-70-TPM2.
|
| | |
| | |
| | |
| | |
| | | |
Using a unit match is racy whereas a syslog identifier match is
reliable.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When running the test on aarch64 the symlinks look as follows:
"""
[root@H ~]# ls /dev/disk/by-path
platform-4010000000.pcie-pci-0000:00:04.0-scsi-0:0:0:0 platform-4010000000.pcie-pci-0000:00:04.0-scsi-0:0:0:0-part1 platform-4010000000.pcie-pci-0000:00:05.0-nvme-16
platform-4010000000.pcie-pci-0000:00:04.0-scsi-0:0:0:0-part platform-4010000000.pcie-pci-0000:00:04.0-scsi-0:0:0:0-part2 platform-4010000000.pcie-pci-0000:00:05.0-nvme-17
"""
So let's make the PCI patterns a little more generic so they match
both the x86 and the aarch64 paths.
|
| | |
| | |
| | |
| | |
| | | |
Let's make sure we pull in multi-user.target so that we get a console
when a test fails and we're running meson test with --interactive.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Using double quotes in f-strings only works from python 3.12 onwards.
Use single quotes to make sure python 3.9 works as well.
Also clean up quotes a little in general.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Trying to use bus pci slot 0 fails on aarch64 so let's use 1 instead.
The error:
"""
qemu-system-aarch64: -device virtio-blk-pci,drive=drive0,scsi=off,bus=pci_bridge25: Unsupported PCI slot 0 for standard hotplug controller. Valid slots are between 1 and 31.
"""
|
|\ \ \
| | | |
| | | | |
A few unrelated cleanups
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
I expect the test output to be the second argument, so we're diffing "expected"
and "output", not the other way around.
I noticed this when working on https://github.com/systemd/systemd/pull/33081.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out OverlayFS doesn't handle gracefully when the same source is
specified multiple times in lowerdir= and it fails with ELOOP:
Failed to mount overlay (type overlay) on /run/systemd/mount-rootfs/opt (MS_RDONLY "lowerdir=/run/systemd/unit-extensions/1/opt:/run/systemd/unit-extensions/0/opt:/run/systemd/mount-rootfs/opt"): Too many levels of symbolic links
This happens even if we mount each image in a different internal mount
path, as OverlayFS will resolve it and look for the backing device, which
will be the same device mapper entity, and return a hard error.
This error does not appear if dm-verity is not used, so it is very
confusing for users, and unnecessary.
When mounting ExtensionImages, check if an image is dm-veritied,
and drop duplicates if the root hashes match, to avoid this user-unfriendly
hard error.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This adds %q, %A and %M specifiers to tmpfiles:
- %A and %M were previously added to tmpfiles.d man page, but not to specifier_table
- %q is added via COMMON_SYSTEM_SPECIFIERS
|
|\ \
| | |
| | | |
core: use write() instead of send()
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
yuwata/network-ndisc-do-not-override-static-routes
network/NDisc: do not override static routes
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
repart: draw progress bar during CopyBlocks= operation and other tweaks
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
importd: add import generator
|
| |/ / / |
|
|/ / /
| | |
| | |
| | | |
Same variable and values as supported by the shell suite
|
|\ \ \
| | | |
| | | | |
machined: unprivileged machine registration
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This mimics what we do in nspawn: if registration is enabled we'll let
machined allocate a scope unit for us. When --keep-unit is used we'll
register without creating a new scope.
This brings behaviour more inline with what nspawn does, exposing the
same sets of options.
|
|/ / |
|
|\ \
| | |
| | | |
core/service: store BUSERROR= & VARLINKERROR= received and show them through systemctl status
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This normalizes how we report an empty list of boot entries in
ListBootEntries(). Our usual pattern is to return one item per method
call, but when there is none we usually return a NoSuchXYZ error. Do so
here too.
Before this we'd return a null item instead here, and only here.
This is a minor compat break, but given that this IPC interface is very
new and probably not used so far (we don't use it in our code at least,
and google doesn#t find any other use) I think this normalization is OK
at this point.
|
| |
| |
| |
| |
| |
| | |
Fixes #33381.
Fixes OSS-FUZZ#69730.
Follow-up for fbb69c0306d434153ca85b227c7d42b9c92872e4.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a symlink is leftover, still allow cleaning it up via 'disable'. This
happens when a unit is stopped and removed, but not disabled, and a reload
has already happened. At that point, cleaning up the old symlinks becomes
impossible through the APIs, and needs to be done manually. Always allow
cleaning up symlinks, if they exist, by only erroring out if there is an
OOM.
Follow-up for f31f10a6207efc9ae9e0b1f73975b5b610914017
|
|\ \
| | |
| | | |
mkosi: enable unprivileged user ns for integration tests
|
| | |
| | |
| | |
| | |
| | | |
mkosi will prefer UEFI if the architecture supports it, but fallback
to 'linux' if it doesn't.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Same as the old integration test suite, allow skipping tests that
require qemu.
ppc64el's vsock support doesn't appear to work, so we'll skip it,
as it is already done in the legacy framework.
|
| | |
| | |
| | |
| | |
| | | |
The shell integration suite allows to manually deselect KVM, so
suppor the same env var for the same purpose in python.
|