nixbot

builds

succeeded container-test-run-tinc-auth-container checks.x86_64-linux.nixos-tinc-auth-container · build #326 · 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 # No journal files were found.18solo # No journal boot entry found for the specified boot (+0).19solo # [1163641.133771] solo systemd-journald[58]: Journal started20solo # [1163641.133815] solo systemd-journald[58]: Runtime Journal (/run/log/journal/d47777d0193948839da0af090e217796) is 8M, max 4G, 3.9G free.21solo # [1163641.138774] solo systemd[1]: Finished Apply Kernel Variables.22solo # [1163641.149295] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.23solo # [1163641.161433] solo systemd[1]: Starting Flush Journal to Persistent Storage...24solo # [1163641.162358] solo systemd[1]: Starting Create Static Device Nodes in /dev...25solo # [1163641.171492] solo systemd-journald[58]: Time spent on flushing to /var/log/journal/d47777d0193948839da0af090e217796 is 1.357ms for 6 entries.26solo # [1163641.171492] solo systemd-journald[58]: System Journal (/var/log/journal/d47777d0193948839da0af090e217796) is 512B, max 4G, 3.9G free.27solo # [1163641.179815] solo systemd[1]: Finished Create Static Device Nodes in /dev.28solo # [1163641.180479] solo systemd[1]: Reached target Preparation for Local File Systems.29solo # [1163641.180603] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys30solo # [1163641.193767] solo systemd[1]: Finished Flush Journal to Persistent Storage.31solo # [1163641.394033] solo systemd[1]: Finished Firewall.32solo # [1163642.138780] solo systemd[1]: Mounting /run/wrappers...33solo # [1163642.159098] solo systemd[1]: Mounted /run/wrappers.34solo # [1163642.174797] solo systemd[1]: Reached target Local File Systems.35solo # [1163642.180557] solo systemd[1]: Listening on Boot Loader Control Service Socket.36solo # [1163642.188501] solo systemd[1]: Starting Create SUID/SGID Wrappers...37solo # [1163642.188542] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container38solo # [1163642.192267] solo systemd[1]: Starting Save Transient machine-id to Disk...39solo # [1163642.196532] solo systemd[1]: Starting Create System Files and Directories...40solo # [1163642.233533] solo systemd-tmpfiles[162]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted41solo # [1163642.233967] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal failed: Operation not permitted42solo # [1163642.235147] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal/d47777d0193948839da0af090e217796 failed: Operation not permitted43solo # [1163642.236288] solo systemd-tmpfiles[162]: fchmod() of /run/log/journal failed: Operation not permitted44solo # [1163642.258070] solo suid-sgid-wrappers-start[169]: chmod: changing permissions of '/run/wrappers/wrappers.VRyqo2STOh/chsh': Operation not permitted45solo # [1163642.327443] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.46solo # [1163642.346289] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE47solo # [1163642.346358] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available48solo # [1163642.346399] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available49solo # [1163642.346427] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.50solo # [1163642.346659] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.51solo # [1163642.346930] solo systemd[1]: Finished Save Transient machine-id to Disk.52solo # [1163642.348646] solo systemd[1]: Finished Create System Files and Directories.53solo # [1163642.464508] solo systemd[1]: Starting Rebuild Journal Catalog...54solo # [1163642.465872] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...55solo # [1163642.483779] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.56solo # [1163642.488054] solo systemd[1]: Finished Rebuild Journal Catalog.57solo # [1163642.498261] solo systemd[1]: Starting Update is Completed...58solo # [1163642.509771] solo systemd[1]: Finished Update is Completed.59solo # [1163642.510027] solo systemd[1]: Reached target System Initialization.60solo # [1163642.510142] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container61solo # [1163642.510180] solo systemd[1]: Started Daily Cleanup of Temporary Directories.62solo # [1163642.510204] solo systemd[1]: Reached target Timer Units.63solo # [1163642.510380] solo systemd[1]: Listening on D-Bus System Message Bus Socket.64solo # [1163642.510644] solo systemd[1]: Listening on Nix Daemon Socket.65solo # [1163642.510821] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.66solo # [1163642.510846] solo systemd[1]: Reached target Socket Units.67solo # [1163642.510896] solo systemd[1]: Reached target Basic System.68solo # [1163642.512667] solo systemd[1]: Starting Import lastlog data into lastlog2 database...69solo # [1163642.514188] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...70solo # [1163642.516906] solo systemd[1]: Starting resolvconf update...71solo # [1163642.523739] solo systemd[1]: Starting Tinc Daemon - mesh...72solo # [1163642.539711] solo tinc.mesh-pre-start[188]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.73solo # [1163642.550273] solo systemd[1]: Started Tinc Daemon - mesh.74solo # [1163642.550724] solo systemd[1]: Finished Import lastlog data into lastlog2 database.75solo # [1163642.557622] solo systemd[1]: Started tinc-auth.service.76solo # [1163642.564890] solo tincd[192]: [INFO tincd] tincd 0.1.0 starting, debug level 077solo # [1163642.565721] solo tincd[192]: [INFO tincd] tincd starting, name=alpha78solo # [1163642.565721] solo tincd[192]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!79solo # [1163642.565721] solo tincd[192]: [INFO tincd] Device mode: Tun, interface: dummy80solo # [1163642.565721] solo tincd[192]: [INFO tincd::net] Listening on 0.0.0.0:65581solo # [1163642.565721] solo tincd[192]: [INFO tincd::net] Listening on [::]:65582solo # [1163642.566092] solo tincd[192]: [INFO tincd] Ready83solo # [1163642.615195] solo tinc-auth[195]: tinc-auth: IdP listening on 127.0.0.1:844384solo # [1163642.623909] solo tinc-auth[195]: tinc-auth: listening (net=mesh)85solo # [1163642.648204] solo systemd[1]: nscd.service: Failed to read pids.max for control group /system.slice/nscd.service, ignoring: No data available86solo # [1163642.648238] solo systemd[1]: nscd.service: Deactivated successfully.87solo # [1163642.651719] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).88solo # [1163642.656724] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...89solo # [1163642.679924] solo systemd[1]: Finished resolvconf update.90solo # [1163642.680113] solo systemd[1]: Reached target Preparation for Network.91solo # [1163642.681315] solo systemd[1]: Starting Address configuration of eth1...92solo # [1163642.684108] solo systemd[1]: Starting Extra networking commands....93solo # [1163642.703034] solo network-addresses-eth1-start[260]: adding address 192.168.1.1/24... done94solo # [1163642.706232] solo network-addresses-eth1-start[260]: adding address 2001:db8:1::1/64... done95solo # [1163642.710762] solo systemd[1]: Finished Address configuration of eth1.96solo # [1163642.806354] solo systemd[1]: Finished Extra networking commands..97solo # [1163642.813548] solo systemd[1]: Reached target Network.98solo # [1163643.870947] solo systemd[1]: Started Name Service Cache Daemon (nsncd).99solo # [1163643.871116] solo systemd[1]: Reached target Host and Network Name Lookups.100solo # [1163643.871881] solo nsncd[251]: Nov 08 21:09:19.915 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"101solo # [1163643.871198] solo systemd[1]: Reached target User and Group Name Lookups.102solo # [1163643.873409] solo systemd[1]: Starting User Login Management...103solo # [1163643.880483] solo systemd[1]: Starting Permit User Sessions...104solo # [1163643.900871] solo systemd[1]: Finished Permit User Sessions.105solo # [1163643.902079] solo systemd[1]: Started Console Getty.106solo # [1163643.902108] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0107solo # [1163643.902122] solo systemd[1]: Reached target Login Prompts.108solo # [1163646.200000] solo systemd-logind[328]: New seat seat0.109solo # [1163646.202232] solo systemd[1]: Starting D-Bus System Message Bus...110solo # [1163646.202700] solo systemd[1]: Started User Login Management.111solo # [1163646.203989] solo systemd[1]: Starting linger-users.service...112solo # [1163646.217348] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available113solo # [1163646.217454] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available114solo # [1163646.217516] solo systemd[1]: linger-users.service: Deactivated successfully.115solo # [1163646.217890] solo systemd[1]: Finished linger-users.service.116solo # [1163646.222052] solo systemd[1]: Reached target Multi-User System.117solo: (finished: waiting for unit tinc.mesh.service, in 6.67 seconds)118solo: waiting for unit tinc-auth.service119solo: (finished: waiting for unit tinc-auth.service, in 0.01 seconds)120solo: waiting for TCP port 8443 on localhost121Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!122solo: (finished: waiting for TCP port 8443 on localhost, in 0.02 seconds)123solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration124solo # [1163646.543454] solo dbus-broker-launch[338]: Looking up NSS user entry for 'systemd-timesync'...125solo # [1163646.544509] solo dbus-broker-launch[338]: NSS returned no entry for 'systemd-timesync'126solo # [1163646.544538] 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"127solo # [1163646.545483] solo systemd[1]: Started D-Bus System Message Bus.128solo # [1163646.545748] solo systemd[1]: Startup finished in 5.907s.129solo # [1163646.558701] solo dbus-broker-launch[338]: Ready130solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.02 seconds)131solo: 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'132solo: (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)133solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=PJevS5KCja69Q9DOwmAqq9SDT5xiVDQKYd6JF72yZX8 -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil134solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=PJevS5KCja69Q9DOwmAqq9SDT5xiVDQKYd6JF72yZX8 -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.02 seconds)135solo: must succeed: curl -fsS -H 'Authorization: Bearer 8QZf3qEeRmfl6xFRFPjyCqFj0gqjwXdz7ey75sgkerU' http://127.0.0.1:8443/userinfo136solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer 8QZf3qEeRmfl6xFRFPjyCqFj0gqjwXdz7ey75sgkerU' http://127.0.0.1:8443/userinfo, in 0.01 seconds)137(finished: run the VM test script, in 6.77 seconds)138test script finished in 7.47s139cleanup140kill NspawnMachine (pid 50)141Container solo terminated by signal KILL.142(finished: cleanup, in 0.58 seconds)143additionally exposed symbols:144 solo,145 vlan1,146 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