shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-02-01 09:47:35 +03:00
Code
systemd/test/units/TEST-13-NSPAWN.machined.sh

417 lines
21 KiB
Bash
Raw Normal View History

test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
#!/usr/bin/env bash
# SPDX-License-Identifier: LGPL-2.1-or-later
# shellcheck disable=SC2016
set -eux
set -o pipefail
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
# shellcheck source=test/units/util.sh
. "$(dirname "$0")"/util.sh
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
export PAGER=
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
at_exit() {
set +e
TEST-13-NSPAWN: several cleanups - suppress unnecessary error messages, especially in loop and at_exit(), - ensure the container service is stopped before restarting, - do not send KILL signal, as garbages will remain, and disturb the next invocation, - drop unnecessary workaround of trying machine twice.
2024-10-15 14:03:02 +09:00
machinectl status long-running &>/dev/null && machinectl kill --signal=KILL long-running
test: use 'until' instead of 'while !' In general, it's better to avoid a negation. And "!" is special, because it is used for history expansion, i.e. the same command would behave differently if pasted on the command line. Inspired by 4a899c5a239eb50df3f596af4ff145f4a2d33f23.
2023-09-06 14:51:07 +02:00
mountpoint -q /var/lib/machines && timeout 10 sh -c "until umount /var/lib/machines; do sleep .5; done"
test: merge machinectl edit/cat tests into TEST-13
2023-05-12 17:59:54 +02:00
[[ -n "${NSPAWN_FRAGMENT:-}" ]] && rm -f "/etc/systemd/nspawn/$NSPAWN_FRAGMENT" "/var/lib/machines/$NSPAWN_FRAGMENT"
test: create nspawn config files when collecting coverage Which bind-mounts the $BUILD_DIR into the container. This whole coverage thing is getting slightly ridiculous. Follow-up to 3b2823a749, but for non-machinectl containers.
2023-05-17 21:49:20 +02:00
rm -f /run/systemd/nspawn/*.nspawn
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
}
trap at_exit EXIT
test: add integration test for importctl (these are explicit tests, on top of the existing machinectl tests that are now chainload importctl)
2024-02-23 22:50:30 +01:00
systemctl service-log-level systemd-machined debug
systemctl service-log-level systemd-importd debug
machine: add debug for systemd-nspawn@.service
2024-11-19 19:12:32 +01:00
# per request in https://github.com/systemd/systemd/pull/35117
systemctl edit --runtime --stdin 'systemd-nspawn@.service' --drop-in=debug.conf <<EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
test: add integration test for importctl (these are explicit tests, on top of the existing machinectl tests that are now chainload importctl)
2024-02-23 22:50:30 +01:00
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
# Mount temporary directory over /var/lib/machines to not pollute the image
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
mkdir -p /var/lib/machines
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
mount --bind "$(mktemp --tmpdir=/var/tmp -d)" /var/lib/machines
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
# Create a couple of containers we can refer to in tests
for i in {0..4}; do
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
create_dummy_container "/var/lib/machines/container$i"
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
machinectl start "container$i"
done
# Create one "long running" container with some basic signal handling
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
create_dummy_container /var/lib/machines/long-running
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
cat >/var/lib/machines/long-running/sbin/init <<\EOF
test: do not fill journal with "wait"
2024-05-17 14:14:00 +09:00
#!/usr/bin/bash
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
PID=0
TEST-13-NSPAWN: trivially kill all processes in the container on termination Follow-up for 841988f80d2440501a3baddba712cdb955225ab7. No functional change, as $PID is 0 when the trap is inserted.
2024-10-25 00:42:28 +09:00
trap 'touch /terminate; kill 0' RTMIN+3
trap 'touch /poweroff' RTMIN+4
trap 'touch /reboot' INT
trap 'touch /trap' TRAP
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
trap 'kill $PID' EXIT
# We need to wait for the sleep process asynchronously in order to allow
# bash to process signals
sleep infinity &
machine: resolve race condition in TEST-13-NSPAWN.machinectl.sh I encountered this race condition while working on TEST-13-NSPAWN.varlinkctl.sh. The long-running machine's init script sometimes does not have time to start and register signals. As result, occasiounally failed tests.
2024-09-20 12:20:53 +02:00
# notify that the process is ready
touch /ready
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
PID=$!
while :; do
wait || :
done
EOF
machine: resolve race condition in TEST-13-NSPAWN.machinectl.sh I encountered this race condition while working on TEST-13-NSPAWN.varlinkctl.sh. The long-running machine's init script sometimes does not have time to start and register signals. As result, occasiounally failed tests.
2024-09-20 12:20:53 +02:00
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
long_running_machine_start() {
# shellcheck disable=SC2015
TEST-13-NSPAWN: several cleanups - suppress unnecessary error messages, especially in loop and at_exit(), - ensure the container service is stopped before restarting, - do not send KILL signal, as garbages will remain, and disturb the next invocation, - drop unnecessary workaround of trying machine twice.
2024-10-15 14:03:02 +09:00
machinectl status long-running &>/dev/null && return 0 || true
# Ensure the service stopped.
systemctl stop systemd-nspawn@long-running.service 2>/dev/null || :
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
rm -f /var/lib/machines/long-running/ready
TEST-13-NSPAWN: several cleanups - suppress unnecessary error messages, especially in loop and at_exit(), - ensure the container service is stopped before restarting, - do not send KILL signal, as garbages will remain, and disturb the next invocation, - drop unnecessary workaround of trying machine twice.
2024-10-15 14:03:02 +09:00
machinectl start long-running
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
# !!!! DO NOT REMOVE THIS TEST
# The test makes sure that the long-running's init script has enough time to start and registered signal traps
timeout 30 bash -c "until test -e /var/lib/machines/long-running/ready; do sleep .5; done"
}
long_running_machine_start
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
machinectl
machinectl --no-pager --help
machinectl --version
machinectl list
machinectl list --no-legend --no-ask-password
machinectl status long-running long-running long-running
machinectl status --full long-running
machinectl status --quiet --lines=1 long-running
machinectl status --lines=0 --max-addresses=0 long-running
machinectl status --machine=testuser@.host long-running
machinectl status --output=help long-running
while read -r output; do
machinectl status --output="$output" long-running
done < <(machinectl --output=help)
machinectl show
machinectl show --all
machinectl show --all --machine=root@
machinectl show --all --machine=testuser@
[[ "$(machinectl show --property=PoolPath --value)" == "/var/lib/machines" ]]
machinectl show long-running
machinectl show long-running long-running long-running --all
[[ "$(machinectl show --property=RootDirectory --value long-running)" == "/var/lib/machines/long-running" ]]
machinectl enable long-running
test -L /etc/systemd/system/machines.target.wants/systemd-nspawn@long-running.service
machinectl enable long-running long-running long-running container1
machinectl disable long-running
test ! -L /etc/systemd/system/machines.target.wants/systemd-nspawn@long-running.service
machinectl disable long-running long-running long-running container1
test: get rid of the busybox stuff It already required a lot of workarounds, since the busybox utilities often work differently than their "full" counterparts, and putting the container together using our "tools" is quite simple anyway.
2023-05-17 19:10:55 +02:00
[[ "$(machinectl shell testuser@ /usr/bin/bash -c 'echo -ne $FOO')" == "" ]]
[[ "$(machinectl shell --setenv=FOO=bar testuser@ /usr/bin/bash -c 'echo -ne $FOO')" == "bar" ]]
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
[[ "$(machinectl show --property=State --value long-running)" == "running" ]]
# Equivalent to machinectl kill --signal=SIGRTMIN+4 --kill-whom=leader
rm -f /var/lib/machines/long-running/poweroff
machinectl poweroff long-running
test: use 'until' instead of 'while !' In general, it's better to avoid a negation. And "!" is special, because it is used for history expansion, i.e. the same command would behave differently if pasted on the command line. Inspired by 4a899c5a239eb50df3f596af4ff145f4a2d33f23.
2023-09-06 14:51:07 +02:00
timeout 10 bash -c "until test -e /var/lib/machines/long-running/poweroff; do sleep .5; done"
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
# Equivalent to machinectl kill --signal=SIGINT --kill-whom=leader
rm -f /var/lib/machines/long-running/reboot
machinectl reboot long-running
test: use 'until' instead of 'while !' In general, it's better to avoid a negation. And "!" is special, because it is used for history expansion, i.e. the same command would behave differently if pasted on the command line. Inspired by 4a899c5a239eb50df3f596af4ff145f4a2d33f23.
2023-09-06 14:51:07 +02:00
timeout 10 bash -c "until test -e /var/lib/machines/long-running/reboot; do sleep .5; done"
TEST-13-NSPAWN: add test for 'machinectl terminate' This also fixes the test for io.systemd.Machine.Terminate. When systemd-nspawn@.service receives stop signal, then systemd-nspawn sends SIGRTMIN+3 to the container, which was previously ignored by the custom init script used by the container. Let's introduce another trap for the signal, and correctly handle it. Follow-up for 164af66f9abdfd8935098d9f10c746ff29dea7df.
2024-10-13 05:15:18 +09:00
# Test for 'machinectl terminate'
rm -f /var/lib/machines/long-running/terminate
machinectl terminate long-running
timeout 10 bash -c "until test -e /var/lib/machines/long-running/terminate; do sleep .5; done"
TEST-13-NSPAWN: several cleanups - suppress unnecessary error messages, especially in loop and at_exit(), - ensure the container service is stopped before restarting, - do not send KILL signal, as garbages will remain, and disturb the next invocation, - drop unnecessary workaround of trying machine twice.
2024-10-15 14:03:02 +09:00
timeout 10 bash -c "while machinectl status long-running &>/dev/null; do sleep .5; done"
TEST-13-NSPAWN: add test for 'machinectl terminate' This also fixes the test for io.systemd.Machine.Terminate. When systemd-nspawn@.service receives stop signal, then systemd-nspawn sends SIGRTMIN+3 to the container, which was previously ignored by the custom init script used by the container. Let's introduce another trap for the signal, and correctly handle it. Follow-up for 164af66f9abdfd8935098d9f10c746ff29dea7df.
2024-10-13 05:15:18 +09:00
# Restart container
long_running_machine_start
# Test for 'machinectl kill'
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
rm -f /var/lib/machines/long-running/trap
machinectl kill --signal=SIGTRAP --kill-whom=leader long-running
test: use 'until' instead of 'while !' In general, it's better to avoid a negation. And "!" is special, because it is used for history expansion, i.e. the same command would behave differently if pasted on the command line. Inspired by 4a899c5a239eb50df3f596af4ff145f4a2d33f23.
2023-09-06 14:51:07 +02:00
timeout 10 bash -c "until test -e /var/lib/machines/long-running/trap; do sleep .5; done"
test: reorder the machinectl signal tests So the multiple-machines tests run last to avoid a race where the checked signal would get ignored while the stub init is still processing the previous signals: [ 17.380417] testsuite-13.sh[376]: + machinectl reboot long-running long-running long-running [ 17.389888] systemd-nspawn[495]: ++ touch /reboot [ 17.390904] testsuite-13.sh[376]: + rm -f /var/lib/machines/long-running/trap [ 17.393937] testsuite-13.sh[376]: + machinectl kill --signal=SIGTRAP --kill-whom=leader long-running [ 17.408905] testsuite-13.sh[376]: + timeout 10 bash -c 'while ! test -e /var/lib/machines/long-running/trap; do sleep .5; done' [ 27.413210] testsuite-13.sh[376]: + at_exit ... [ 27.993376] testsuite-13.sh[373]: + echo 'Subtest /usr/lib/systemd/tests/testdata/units/testsuite-13.machinectl.sh failed'
2023-07-10 10:39:00 +02:00
# Multiple machines at once
machinectl poweroff long-running long-running long-running
machinectl reboot long-running long-running long-running
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
machinectl kill --signal=SIGTRAP --kill-whom=leader long-running long-running long-running
# All used signals should've been caught by a handler
[[ "$(machinectl show --property=State --value long-running)" == "running" ]]
cp /etc/machine-id /tmp/foo
machinectl copy-to long-running /tmp/foo /root/foo
test -f /var/lib/machines/long-running/root/foo
machinectl copy-from long-running /root/foo /tmp/bar
diff /tmp/foo /tmp/bar
rm -f /tmp/{foo,bar}
# machinectl bind is covered by testcase_check_machinectl_bind() in nspawn tests
machinectl list-images
machinectl list-images --no-legend
machinectl image-status
machinectl image-status container1
machinectl image-status container1 container1 container{0..4}
machinectl show-image
machinectl show-image container1
machinectl show-image container1 container1 container{0..4}
machinectl clone container1 clone1
machinectl show-image clone1
machinectl rename clone1 clone2
(! machinectl show-image clone1)
machinectl show-image clone2
test: add a brief comment for the chattr check Addresses: https://github.com/systemd/systemd/pull/32907#discussion_r1605919598
2024-05-21 15:08:07 +02:00
# `machinectl read-only` uses chattr (ioctl(FS_IOC_SETFLAGS)) when the container is backed by a directory,
# and this operation might not be implemented on certain filesystems (i.e. tmpfs on older kernels), so check
# if we have chattr support before running following tests
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
if lsattr -d /var/lib/machines >/dev/null; then
[[ "$(machinectl show-image --property=ReadOnly --value clone2)" == no ]]
machinectl read-only clone2 yes
[[ "$(machinectl show-image --property=ReadOnly --value clone2)" == yes ]]
machinectl read-only clone2 no
[[ "$(machinectl show-image --property=ReadOnly --value clone2)" == no ]]
fi
machinectl remove clone2
for i in {0..4}; do
machinectl clone container1 "clone$i"
done
machinectl remove clone{0..4}
for i in {0..4}; do
machinectl clone container1 ".hidden$i"
done
machinectl list-images --all
test -d /var/lib/machines/.hidden1
machinectl clean
test ! -d /var/lib/machines/.hidden1
# Prepare a simple raw container
mkdir -p /tmp/mnt
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
dd if=/dev/zero of=/var/tmp/container.raw bs=1M count=256
mkfs.ext4 /var/tmp/container.raw
mount -o loop /var/tmp/container.raw /tmp/mnt
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
cp -r /var/lib/machines/container1/* /tmp/mnt
umount /tmp/mnt
# Try to import it, run it, export it, and re-import it
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
machinectl import-raw /var/tmp/container.raw container-raw
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
[[ "$(machinectl show-image --property=Type --value container-raw)" == "raw" ]]
machinectl start container-raw
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
machinectl export-raw container-raw /var/tmp/container-export.raw
machinectl import-raw /var/tmp/container-export.raw container-raw-reimport
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
[[ "$(machinectl show-image --property=Type --value container-raw-reimport)" == "raw" ]]
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
rm -f /var/tmp/container{,-export}.raw
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
# Prepare a simple tar.gz container
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
tar -pczf /var/tmp/container.tar.gz -C /var/lib/machines/container1 .
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
# Try to import it, run it, export it, and re-import it
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
machinectl import-tar /var/tmp/container.tar.gz container-tar
[[ "$(machinectl show-image --property=Type --value container-tar)" =~ directory|subvolume ]]
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
machinectl start container-tar
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
machinectl export-tar container-tar /var/tmp/container-export.tar.gz
machinectl import-tar /var/tmp/container-export.tar.gz container-tar-reimport
[[ "$(machinectl show-image --property=Type --value container-tar-reimport)" =~ directory|subvolume ]]
rm -f /var/tmp/container{,-export}.tar.gz
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
# Try to import a container directory & run it
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
cp -r /var/lib/machines/container1 /var/tmp/container.dir
machinectl import-fs /var/tmp/container.dir container-dir
[[ "$(machinectl show-image --property=Type --value container-dir)" =~ directory|subvolume ]]
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
machinectl start container-dir
TEST-13-NSPAWN: move disk images to /var/tmp /tmp may not be large enough to contain disk images and will result in strange errors when it runs out of space.
2024-02-13 12:48:26 +00:00
rm -fr /var/tmp/container.dir
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
test: use 'until' instead of 'while !' In general, it's better to avoid a negation. And "!" is special, because it is used for history expansion, i.e. the same command would behave differently if pasted on the command line. Inspired by 4a899c5a239eb50df3f596af4ff145f4a2d33f23.
2023-09-06 14:51:07 +02:00
timeout 10 bash -c "until machinectl clean --all; do sleep .5; done"
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
test: merge machinectl edit/cat tests into TEST-13
2023-05-12 17:59:54 +02:00
NSPAWN_FRAGMENT="machinectl-test-$RANDOM.nspawn"
cat >"/var/lib/machines/$NSPAWN_FRAGMENT" <<EOF
[Exec]
Boot=true
EOF
machinectl cat "$NSPAWN_FRAGMENT"
EDITOR=true script -qec "machinectl edit $NSPAWN_FRAGMENT" /dev/null
test -f "/etc/systemd/nspawn/$NSPAWN_FRAGMENT"
diff "/var/lib/machines/$NSPAWN_FRAGMENT" "/etc/systemd/nspawn/$NSPAWN_FRAGMENT"
cat >/tmp/fragment.nspawn <<EOF
[Exec]
Boot=false
EOF
machinectl cat /tmp/fragment.nspawn
EDITOR="cp /tmp/fragment.nspawn" script -qec "machinectl edit $NSPAWN_FRAGMENT" /dev/null
diff /tmp/fragment.nspawn "/etc/systemd/nspawn/$NSPAWN_FRAGMENT"
test: add a couple of tests for machinectl
2023-05-12 17:39:41 +02:00
for opt in format lines machine max-addresses output setenv verify; do
(! machinectl status "--$opt=" long-running)
(! machinectl status "--$opt=-1" long-running)
(! machinectl status "--$opt=''" long-running)
done
(! machinectl show "")
(! machinectl enable)
(! machinectl enable "")
(! machinectl disable)
(! machinectl disable "")
(! machinectl read-only container1 "")
(! machinectl read-only container1 foo)
(! machinectl read-only container1 -- -1)
test: add some superficial integration tests
2024-05-23 23:19:12 +02:00
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
####################
# varlinkctl tests #
# ##################
long_running_machine_start
machine: add MachineImage interface Follow-up for fb0ea6a6a36b5fa97e6c57d608bb9f7acb63c8b2. Fixes #34772.
2024-10-15 17:39:00 +09:00
varlinkctl introspect /run/systemd/machine/io.systemd.Machine io.systemd.Machine
varlinkctl introspect /run/systemd/machine/io.systemd.Machine io.systemd.MachineImage
varlinkctl introspect /run/systemd/machine/io.systemd.MachineImage io.systemd.Machine
varlinkctl introspect /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
# test io.systemd.Machine.List
varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{}' | grep 'long-running'
varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{}' | grep '.host'
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"long-running"}'
machined: port all varlink APIs over to new PidRef serialization
2024-10-11 13:51:25 +02:00
pid=$(varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"long-running"}' | jq '.leader')
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"long-running"}' >/tmp/expected
machine: lookup_machine_by_name_or_pid() may return 1 on error and it is already replied Follow-ups for 1bd979dddbb6ed3ffe410d78a7ff80cbb1c42a64 and later commits. Fixes #34764.
2024-10-15 11:20:13 +09:00
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List "{\"pid\":$pid}" | diff /tmp/expected -
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List "{\"name\":\"long-running\", \"pid\":$pid}" | diff /tmp/expected -
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List "{\"name\":\"non-existent\", \"pid\":$pid}")
machine: lookup_machine_by_name_or_pid() may return 1 on error and it is already replied Follow-ups for 1bd979dddbb6ed3ffe410d78a7ff80cbb1c42a64 and later commits. Fixes #34764.
2024-10-15 11:20:13 +09:00
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":""}')
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"ah@??.hmm"}')
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
# test io.systemd.Machine.Kill
# sending TRAP signal
rm -f /var/lib/machines/long-running/trap
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Kill '{"name":"long-running", "whom": "leader", "signal": 5}'
machine: increase timeouts in attempt to fix #35115
2024-11-11 15:13:55 +01:00
timeout 120 bash -c "until test -e /var/lib/machines/long-running/trap; do sleep .5; done"
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
# test io.systemd.Machine.Terminate
long_running_machine_start
TEST-13-NSPAWN: add test for 'machinectl terminate' This also fixes the test for io.systemd.Machine.Terminate. When systemd-nspawn@.service receives stop signal, then systemd-nspawn sends SIGRTMIN+3 to the container, which was previously ignored by the custom init script used by the container. Let's introduce another trap for the signal, and correctly handle it. Follow-up for 164af66f9abdfd8935098d9f10c746ff29dea7df.
2024-10-13 05:15:18 +09:00
rm -f /var/lib/machines/long-running/terminate
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Terminate '{"name":"long-running"}'
machine: increase timeouts in attempt to fix #35115
2024-11-11 15:13:55 +01:00
timeout 30 bash -c "until test -e /var/lib/machines/long-running/terminate; do sleep .5; done"
TEST-13-NSPAWN: add test for 'machinectl terminate' This also fixes the test for io.systemd.Machine.Terminate. When systemd-nspawn@.service receives stop signal, then systemd-nspawn sends SIGRTMIN+3 to the container, which was previously ignored by the custom init script used by the container. Let's introduce another trap for the signal, and correctly handle it. Follow-up for 164af66f9abdfd8935098d9f10c746ff29dea7df.
2024-10-13 05:15:18 +09:00
timeout 30 bash -c "while varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{\"name\":\"long-running\"}'; do sleep 0.5; done"
machine: tests for varlink interfaces - io.systemd.Machine.List - io.systemd.Machine.Kill - io.systemd.Machine.Terminate - io.systemd.Machine.Register - io.systemd.Machine.Unregister
2024-10-07 11:35:32 +02:00
# test io.systemd.Machine.Register
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Register '{"name": "registered-container", "class": "container"}'
timeout 30 bash -c "until varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{\"name\":\"registered-container\"}'; do sleep 0.5; done"
# test io.systemd.Machine.Unregister
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Unregister '{"name": "registered-container"}'
timeout 30 bash -c "while varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{\"name\":\"registered-container\"}'; do sleep 0.5; done"
# test io.systemd.Machine.List with sshAddress and sshPrivateKeyPath fields
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Register '{"name": "registered-container", "class": "container", "sshAddress": "localhost", "sshPrivateKeyPath": "/non-existent"}'
timeout 30 bash -c "until varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{\"name\":\"registered-container\"}'; do sleep 0.5; done"
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"registered-container"}' | jq '.sshAddress' | grep -q 'localhost'
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name":"registered-container"}' | jq '.sshPrivateKeyPath' | grep -q 'non-existent'
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Unregister '{"name": "registered-container"}'
machine: tests for varlink interfaces - io.systemd.MachineImage.List - io.systemd.MachineImage.Update
2024-10-08 17:00:27 +02:00
machine: add tests for Addresses/OSRelease/UIDShift fields in io.systemd.Machine.List output
2024-10-17 13:56:43 +02:00
# test io.systemd.Machine.List with addresses, OSRelease, and UIDShift fields
create_dummy_container "/var/lib/machines/container-without-os-release"
TEST-13-NSPAWN: fix race between container exit and varlink call Follow-up for 3cb72c7862d8950bc2a963aaa3ca3255eea374b6. The test container exits shortly, hence when varlinkctl is called, the container may be already terminated. Let's make the container live infinitely. Also, this makes the os-release files removed after the container is started.
2024-10-24 06:00:53 +09:00
cat >>/var/lib/machines/container-without-os-release/sbin/init <<\EOF
TEST-13-NSPAWN: check returned machine list
2024-10-25 00:24:04 +09:00
ip link add hoge type dummy
ip link set hoge up
ip address add 192.0.2.1/24 dev hoge
TEST-13-NSPAWN: fix race between container exit and varlink call Follow-up for 3cb72c7862d8950bc2a963aaa3ca3255eea374b6. The test container exits shortly, hence when varlinkctl is called, the container may be already terminated. Let's make the container live infinitely. Also, this makes the os-release files removed after the container is started.
2024-10-24 06:00:53 +09:00
PID=0
trap 'kill 0' RTMIN+3
trap 'kill $PID' EXIT
# We need to wait for the sleep process asynchronously in order to allow
# bash to process signals
sleep infinity &
# notify that the process is ready
touch /ready
PID=$!
while :; do
wait || :
done
EOF
machine: add tests for Addresses/OSRelease/UIDShift fields in io.systemd.Machine.List output
2024-10-17 13:56:43 +02:00
machinectl start "container-without-os-release"
TEST-13-NSPAWN: fix race between container exit and varlink call Follow-up for 3cb72c7862d8950bc2a963aaa3ca3255eea374b6. The test container exits shortly, hence when varlinkctl is called, the container may be already terminated. Let's make the container live infinitely. Also, this makes the os-release files removed after the container is started.
2024-10-24 06:00:53 +09:00
timeout 30 bash -c "until test -e /var/lib/machines/container-without-os-release/ready; do sleep .5; done"
machine: add tests for Addresses/OSRelease/UIDShift fields in io.systemd.Machine.List output
2024-10-17 13:56:43 +02:00
rm -f /var/lib/machines/container-without-os-release/etc/os-release /var/lib/machines/container-without-os-release/usr/lib/os-release
(! varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": "container-without-os-release", "acquireMetadata": "yes"}')
TEST-13-NSPAWN: check returned machine list
2024-10-25 00:24:04 +09:00
output=$(varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": "container-without-os-release", "acquireMetadata": "graceful"}')
assert_eq "$(echo "$output" | jq --seq .name | tr -d \\036)" '"container-without-os-release"'
assert_eq "$(echo "$output" | jq --seq .class | tr -d \\036)" '"container"'
assert_eq "$(echo "$output" | jq --seq .service | tr -d \\036)" '"systemd-nspawn"'
assert_eq "$(echo "$output" | jq --seq .rootDirectory | tr -d \\036)" '"/var/lib/machines/container-without-os-release"'
assert_eq "$(echo "$output" | jq --seq .unit | tr -d \\036)" '"systemd-nspawn@container-without-os-release.service"'
assert_eq "$(echo "$output" | jq --seq .addresses[0].family | tr -d \\036)" '2'
assert_eq "$(echo "$output" | jq --seq .addresses[0].address[0] | tr -d \\036)" '192'
assert_eq "$(echo "$output" | jq --seq .addresses[0].address[1] | tr -d \\036)" '0'
assert_eq "$(echo "$output" | jq --seq .addresses[0].address[2] | tr -d \\036)" '2'
assert_eq "$(echo "$output" | jq --seq .addresses[0].address[3] | tr -d \\036)" '1'
TEST-13-NSPAWN: add test cases for listing multiple machines
2024-10-31 11:02:23 +09:00
# test for listing multiple machines.
long_running_machine_start
varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{}'
varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"acquireMetadata": "no"}'
varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"acquireMetadata": "graceful"}'
# check if machined does not try to send anything after error message
journalctl --sync
TS="$(date '+%H:%M:%S')"
(! varlinkctl --more call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"acquireMetadata": "yes"}')
journalctl --sync
(! journalctl -u systemd-machined.service --since="$TS" --grep 'Connection busy')
# terminate machines
machinectl terminate container-without-os-release
machinectl terminate long-running
# wait for the container being stopped, otherwise acquiring image metadata by io.systemd.MachineImage.List may fail in the below.
machine: increase timeouts in attempt to fix #35115
2024-11-11 15:13:55 +01:00
timeout 30 bash -c "while machinectl status long-running &>/dev/null; do sleep .5; done"
TEST-13-NSPAWN: add test cases for listing multiple machines
2024-10-31 11:02:23 +09:00
systemctl kill --signal=KILL systemd-nspawn@long-running.service || :
machine: add tests for Addresses/OSRelease/UIDShift fields in io.systemd.Machine.List output
2024-10-17 13:56:43 +02:00
(ip addr show lo | grep -q 192.168.1.100) || ip address add 192.168.1.100/24 dev lo
machine: remove redundant --more in TEST-13-NSPAWN.machined
2024-10-22 11:16:53 +02:00
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host"}' | grep 'addresses')
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host", "acquireMetadata": "yes"}' | grep 'addresses'
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host"}' | grep 'OSRelease')
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host", "acquireMetadata": "yes"}' | grep 'OSRelease'
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host"}' | grep 'acquireUIDShift')
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.List '{"name": ".host", "acquireMetadata": "yes"}' | grep 'UIDShift'
machine: add tests for Addresses/OSRelease/UIDShift fields in io.systemd.Machine.List output
2024-10-17 13:56:43 +02:00
machine: tests for io.systemd.Machine.Open
2024-10-23 16:02:26 +02:00
# test io.systemd.Machine.Open
# Reducing log level here is to work-around check in end.service (end.sh). Read https://github.com/systemd/systemd/pull/34867 for more details
systemctl service-log-level systemd-machined info
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host"}')
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": ""}')
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": null}')
(! varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": "foo"}')
systemctl service-log-level systemd-machined debug
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": "tty"}'
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": "login"}'
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": "shell"}'
rm -f /tmp/none-existent-file
varlinkctl call /run/systemd/machine/io.systemd.Machine io.systemd.Machine.Open '{"name": ".host", "mode": "shell", "user": "root", "path": "/bin/sh", "args": ["/bin/sh", "-c", "echo $FOO > /tmp/none-existent-file"], "environment": ["FOO=BAR"]}'
timeout 30 bash -c "until test -e /tmp/none-existent-file; do sleep .5; done"
grep -q "BAR" /tmp/none-existent-file
machine: tests for varlink interfaces - io.systemd.MachineImage.List - io.systemd.MachineImage.Update
2024-10-08 17:00:27 +02:00
# test io.systemd.MachineImage.List
varlinkctl --more call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{}' | grep 'long-running'
varlinkctl --more call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{}' | grep '.host'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running"}'
machine: use AcquireMetadata in io.systemd.MachineImage.List method
2024-10-17 13:56:25 +02:00
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running", "acquireMetadata": "yes"}' | grep 'OSRelease'
machine: tests for varlink interfaces - io.systemd.MachineImage.List - io.systemd.MachineImage.Update
2024-10-08 17:00:27 +02:00
# test io.systemd.MachineImage.Update
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.Update '{"name":"long-running", "newName": "long-running-renamed", "readOnly": true}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running-renamed"}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running-renamed"}' | jq '.readOnly' | grep 'true'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.Update '{"name":"long-running-renamed", "newName": "long-running", "readOnly": false}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running"}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running"}' | jq '.readOnly' | grep 'false'
machine: tests for io.systemd.MachineImage.{Clone, Remove} methods
2024-10-21 13:58:30 +02:00
# test io.systemd.MachineImage.Clone
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.Clone '{"name":"long-running", "newName": "long-running-cloned", "readOnly": true}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running-cloned"}'
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running-cloned"}' | jq '.readOnly' | grep 'true'
# test io.systemd.MachineImage.Remove
varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.Remove '{"name":"long-running-cloned"}'
(! varlinkctl call /run/systemd/machine/io.systemd.MachineImage io.systemd.MachineImage.List '{"name":"long-running-cloned"}')
Copy Permalink