container-test-run-tinc-auth-container
checks.x86_64-linux.nixos-tinc-auth-container
· build #325
· raw
1tribuchet: building on jamie2Machine state will be reset. To keep it, pass --keep-machine-state3start all VLans4(finished: start all VLans, in 0.00 seconds)5Initializing machine ID from random generator.6Test will time out and terminate in 3600.0 seconds7run the VM test script8start all VMs9solo: systemd-nspawn running (pid 50)10solo: Waiting for journal at /build/vm-state-solo/var/log/journal...11(finished: start all VMs, in 0.00 seconds)12solo: waiting for unit tinc.mesh.service13nixos-nspawn(solo): TAP vde-tap1 not found; container will be isolated from VDE14nixos-nspawn(solo): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.15Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.16░ Spawning container solo on /build/vm-state-solo.17solo # [1163503.652259] solo systemd-journald[58]: Journal started18solo # [1163503.652305] solo systemd-journald[58]: Runtime Journal (/run/log/journal/48e86ea816fc498b87e19ddf230c3985) is 8M, max 4G, 3.9G free.19solo # [1163503.664262] solo systemd[1]: Finished Apply Kernel Variables.20solo # [1163503.678704] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.21solo # [1163503.691050] solo systemd[1]: Starting Flush Journal to Persistent Storage...22solo # [1163503.691978] solo systemd[1]: Starting Create Static Device Nodes in /dev...23solo # [1163503.700166] solo systemd-journald[58]: Time spent on flushing to /var/log/journal/48e86ea816fc498b87e19ddf230c3985 is 1.473ms for 6 entries.24solo # [1163503.700166] solo systemd-journald[58]: System Journal (/var/log/journal/48e86ea816fc498b87e19ddf230c3985) is 512B, max 4G, 3.9G free.25solo # [1163503.714223] solo systemd[1]: Finished Create Static Device Nodes in /dev.26solo # [1163503.714970] solo systemd[1]: Reached target Preparation for Local File Systems.27solo # [1163503.715097] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys28solo # [1163503.723058] solo systemd[1]: Finished Flush Journal to Persistent Storage.29solo # [1163503.870526] solo systemd[1]: Finished Firewall.30solo # [1163504.854890] solo systemd[1]: Mounting /run/wrappers...31solo # [1163504.949265] solo systemd[1]: Mounted /run/wrappers.32solo # [1163504.950756] solo systemd[1]: Reached target Local File Systems.33solo # [1163504.952136] solo systemd[1]: Listening on Boot Loader Control Service Socket.34solo # [1163504.957971] solo systemd[1]: Starting Create SUID/SGID Wrappers...35solo # [1163504.958052] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container36solo # [1163504.959505] solo systemd[1]: Starting Save Transient machine-id to Disk...37solo # [1163504.964836] solo systemd[1]: Starting Create System Files and Directories...38solo # [1163504.988167] solo systemd-tmpfiles[162]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted39solo # [1163504.988858] solo suid-sgid-wrappers-start[169]: chmod: changing permissions of '/run/wrappers/wrappers.5y0DXN9lCf/chsh': Operation not permitted40solo # [1163504.989157] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal failed: Operation not permitted41solo # [1163504.989487] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal/48e86ea816fc498b87e19ddf230c3985 failed: Operation not permitted42solo # [1163504.989866] solo systemd-tmpfiles[162]: fchmod() of /run/log/journal failed: Operation not permitted43solo # [1163505.000152] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE44solo # [1163505.000246] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available45solo # [1163505.000330] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available46solo # [1163505.000374] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.47solo # [1163505.000691] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.48solo # [1163505.001438] solo systemd[1]: Finished Create System Files and Directories.49solo # [1163505.029174] solo systemd[1]: Starting Rebuild Journal Catalog...50solo # [1163505.030061] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...51solo # [1163505.046061] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.52solo # [1163505.051306] solo systemd[1]: Finished Rebuild Journal Catalog.53solo # [1163505.052702] solo systemd[1]: Starting Update is Completed...54solo # [1163505.078125] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.55solo # [1163505.079047] solo systemd[1]: Finished Save Transient machine-id to Disk.56solo # [1163505.079339] solo systemd[1]: Finished Update is Completed.57solo # [1163505.087283] solo systemd[1]: Reached target System Initialization.58solo # [1163505.087404] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container59solo # [1163505.087434] solo systemd[1]: Started Daily Cleanup of Temporary Directories.60solo # [1163505.087454] solo systemd[1]: Reached target Timer Units.61solo # [1163505.087598] solo systemd[1]: Listening on D-Bus System Message Bus Socket.62solo # [1163505.087860] solo systemd[1]: Listening on Nix Daemon Socket.63solo # [1163505.088263] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.64solo # [1163505.088286] solo systemd[1]: Reached target Socket Units.65solo # [1163505.088333] solo systemd[1]: Reached target Basic System.66solo # [1163505.095616] solo systemd[1]: Starting Import lastlog data into lastlog2 database...67solo # [1163505.097352] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...68solo # [1163505.098736] solo systemd[1]: Starting resolvconf update...69solo # [1163505.099923] solo systemd[1]: Starting Tinc Daemon - mesh...70solo # [1163505.123280] solo tinc.mesh-pre-start[188]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.71solo # [1163505.125354] solo systemd[1]: Started Tinc Daemon - mesh.72solo # [1163505.125627] solo systemd[1]: Finished Import lastlog data into lastlog2 database.73solo # [1163505.127404] solo systemd[1]: Started tinc-auth.service.74solo # [1163505.134374] solo tincd[191]: [INFO tincd] tincd 0.1.0 starting, debug level 075solo # [1163505.134877] solo tincd[191]: [INFO tincd] tincd starting, name=alpha76solo # [1163505.134877] solo tincd[191]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!77solo # [1163505.134877] solo tincd[191]: [INFO tincd] Device mode: Tun, interface: dummy78solo # [1163505.134877] solo tincd[191]: [INFO tincd::net] Listening on 0.0.0.0:65579solo # [1163505.134877] solo tincd[191]: [INFO tincd::net] Listening on [::]:65580solo # [1163505.134877] solo tincd[191]: [INFO tincd] Ready81solo # [1163505.183448] solo systemd[1]: nscd.service: Failed to read pids.max for control group /system.slice/nscd.service, ignoring: No data available82solo # [1163505.183484] solo systemd[1]: nscd.service: Deactivated successfully.83solo # [1163505.183710] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).84solo # [1163505.187094] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...85solo # [1163505.203250] solo tinc-auth[194]: tinc-auth: IdP listening on 127.0.0.1:844386solo # [1163505.204111] solo tinc-auth[194]: tinc-auth: listening (net=mesh)87solo # [1163505.204300] solo systemd[1]: Finished resolvconf update.88solo # [1163505.204488] solo systemd[1]: Reached target Preparation for Network.89solo # [1163505.205902] solo systemd[1]: Starting Address configuration of eth1...90solo # [1163505.206890] solo systemd[1]: Starting Extra networking commands....91solo # [1163505.229960] solo network-addresses-eth1-start[260]: adding address 192.168.1.1/24... done92solo # [1163505.233459] solo network-addresses-eth1-start[260]: adding address 2001:db8:1::1/64... done93solo # [1163505.239355] solo systemd[1]: Finished Address configuration of eth1.94solo # [1163505.309501] solo systemd[1]: Finished Extra networking commands..95solo # [1163505.312351] solo systemd[1]: Reached target Network.96solo # [1163505.575480] solo nsncd[242]: Nov 08 21:07:01.620 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"97solo # [1163505.575573] solo systemd[1]: Started Name Service Cache Daemon (nsncd).98solo # [1163505.575634] solo systemd[1]: Reached target Host and Network Name Lookups.99solo # [1163505.575702] solo systemd[1]: Reached target User and Group Name Lookups.100solo # [1163505.577308] solo systemd[1]: Starting User Login Management...101solo # [1163505.578204] solo systemd[1]: Starting Permit User Sessions...102solo # [1163505.592247] solo systemd[1]: Finished Permit User Sessions.103solo # [1163505.593495] solo systemd[1]: Started Console Getty.104solo # [1163505.593534] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0105solo # [1163505.593556] solo systemd[1]: Reached target Login Prompts.106solo # [1163507.167381] solo systemd-logind[328]: New seat seat0.107solo # [1163507.168259] solo systemd[1]: Started User Login Management.108solo # [1163507.170393] solo systemd[1]: Starting D-Bus System Message Bus...109solo # [1163507.171797] solo systemd[1]: Starting linger-users.service...110solo # [1163507.185807] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available111solo # [1163507.185852] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available112solo # [1163507.185881] solo systemd[1]: linger-users.service: Deactivated successfully.113solo # [1163507.186125] solo systemd[1]: Finished linger-users.service.114solo # [1163507.186324] solo systemd[1]: Reached target Multi-User System.115solo # [1163507.577730] solo dbus-broker-launch[338]: Looking up NSS user entry for 'systemd-timesync'...116solo # [1163507.578908] solo dbus-broker-launch[338]: NSS returned no entry for 'systemd-timesync'117solo # [1163507.578908] solo dbus-broker-launch[338]: Invalid user-name in /nix/store/75mffjd6kbm4i4a88halibgbr9z3aaww-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"118solo # [1163507.579803] solo systemd[1]: Started D-Bus System Message Bus.119solo # [1163507.580152] solo systemd[1]: Startup finished in 4.281s.120solo # [1163507.584846] solo dbus-broker-launch[338]: Ready121solo: (finished: waiting for unit tinc.mesh.service, in 5.16 seconds)122solo: waiting for unit tinc-auth.service123solo: (finished: waiting for unit tinc-auth.service, in 0.03 seconds)124solo: waiting for TCP port 8443 on localhost125Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!126solo: (finished: waiting for TCP port 8443 on localhost, in 0.01 seconds)127solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration128solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.02 seconds)129solo: must succeed: curl -fsS -o /dev/null -w '%{redirect_url}' 'http://127.0.0.1:8443/authorize?response_type=code&client_id=app&redirect_uri=http%3A%2F%2Fapp.example%2Fcb&state=s'130solo: (finished: must succeed: curl -fsS -o /dev/null -w '%{redirect_url}' 'http://127.0.0.1:8443/authorize?response_type=code&client_id=app&redirect_uri=http%3A%2F%2Fapp.example%2Fcb&state=s', in 0.02 seconds)131solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=wzVns6BQz42VESG4Jvyz_7XjDldABUdFgtaUpWSaZ6M -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil132solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=wzVns6BQz42VESG4Jvyz_7XjDldABUdFgtaUpWSaZ6M -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.02 seconds)133solo: must succeed: curl -fsS -H 'Authorization: Bearer 5cLhfSIvmKSvpv-w2gSJmxyQYnlGgsybvGFYFdoHDQ0' http://127.0.0.1:8443/userinfo134solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer 5cLhfSIvmKSvpv-w2gSJmxyQYnlGgsybvGFYFdoHDQ0' http://127.0.0.1:8443/userinfo, in 0.02 seconds)135(finished: run the VM test script, in 5.28 seconds)136test script finished in 5.44s137cleanup138kill NspawnMachine (pid 50)139Container solo terminated by signal KILL.140(finished: cleanup, in 0.77 seconds)141additionally exposed symbols:142 solo,143 vlan1,144 start_all, test_script, machines, machines_qemu, machines_nspawn, vlans, driver, log, os, create_machine, subtest, run_tests, join_all, retry, serial_stdout_off, serial_stdout_on, polling_condition, BaseMachine, QemuMachine, NspawnMachine, t, debug, dump_machine_ssh