tests: verify systemd-sysuser.service will be triggered with new

deployment

See ostreedev/ostree#3069 (comment)

tests/kola/systemd/condition-needs-update

@@ -0,0 +1,55 @@
+#!/bin/bash
+## kola:
+##   description: Verify systemd-sysuser.service is triggered with new 
+##     deployment at boot time.
+
+# See https://github.com/ostreedev/ostree/issues/3069#issuecomment-1798115799
+# As the update trigger condition is /usr/'s modification time should be newer
+# than /etc/.updated & /var/.updated files, but /usr/'s modification time is
+# always the same as the .updated files according to
+# https://ostreedev.github.io/ostree/repo/#content-objects
+
+# Fixed by https://github.com/ostreedev/ostree/commit/19d18842cf2df944c7e9536494353aefa2916743, 
+# we always remove .updated files from new deployments so the the condition
+# always triggers.
+
+set -xeuo pipefail
+
+. "$KOLA_EXT_DATA/commonlib.sh"
+
+username=footest
+
+case "${AUTOPKGTEST_REBOOT_MARK:-}" in
+  "")
+    ok "first boot"
+    if getent passwd ${username}; then
+      fatal "should not get user ${username} before testing"
+    fi
+    # create sysusers config
+    mkdir /etc/sysusers.d
+    echo "u      ${username}  -   ${username}" > /etc/sysusers.d/30-${username}.conf
+    /tmp/autopkgtest-reboot second-boot
+    ;;
+
+  second-boot)
+    # reboot to check user footest not created
+    ok "second boot"
+    if getent passwd ${username}; then
+      fatal "should not get user ${username} after second boot"
+    fi
+    # create a new deployment
+    ref=$(rpm-ostree status --json | jq -r '.deployments[0].origin')
+    ostree admin deploy --karg-append=somedummykarg=1 $ref
+    /tmp/autopkgtest-reboot third-boot
+    ;;
+
+  third-boot)
+    ok "third boot"
+    # check user footest is created
+    if ! getent passwd ${username}; then
+      fatal "should get user ${username} with new deployment after third boot"
+    fi
+    ;;
+
+    *) fatal "unexpected mark: ${AUTOPKGTEST_REBOOT_MARK}";;
+esac