container-test-run-tinc-auth-container
checks.aarch64-linux.nixos-tinc-auth-container
· build #332
· raw
1tribuchet: building on eliza2Machine state will be reset. To keep it, pass --keep-machine-state3start all VLans4(finished: start all VLans, in 1.27 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 1.56 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 # No journal files were found.20solo # No journal boot entry found for the specified boot (+0).21solo # No journal files were found.22solo # No journal boot entry found for the specified boot (+0).23solo # No journal files were found.24solo # No journal boot entry found for the specified boot (+0).25solo # No journal files were found.26solo # No journal boot entry found for the specified boot (+0).27solo # No journal files were found.28solo # No journal boot entry found for the specified boot (+0).29solo # No journal files were found.30solo # No journal boot entry found for the specified boot (+0).31solo # No journal files were found.32solo # No journal boot entry found for the specified boot (+0).33solo # No journal files were found.34solo # No journal boot entry found for the specified boot (+0).35solo # No journal files were found.36solo # No journal boot entry found for the specified boot (+0).37solo: still waiting for container 'solo' to reach ready state...38solo # No journal files were found.39solo # No journal boot entry found for the specified boot (+0).40solo # No journal files were found.41solo # No journal boot entry found for the specified boot (+0).42solo # No journal files were found.43solo # No journal boot entry found for the specified boot (+0).44solo # No journal files were found.45solo # No journal boot entry found for the specified boot (+0).46solo # No journal files were found.47solo # No journal boot entry found for the specified boot (+0).48solo # No journal files were found.49solo # No journal boot entry found for the specified boot (+0).50solo # No journal files were found.51solo # No journal boot entry found for the specified boot (+0).52solo # No journal files were found.53solo # No journal boot entry found for the specified boot (+0).54solo # No journal files were found.55solo # No journal boot entry found for the specified boot (+0).56solo # No journal files were found.57solo # No journal boot entry found for the specified boot (+0).58solo: still waiting for container 'solo' to reach ready state...59solo # No journal files were found.60solo # No journal boot entry found for the specified boot (+0).61solo # No journal files were found.62solo # No journal boot entry found for the specified boot (+0).63solo # No journal files were found.64solo # No journal boot entry found for the specified boot (+0).65solo # No journal files were found.66solo # No journal boot entry found for the specified boot (+0).67solo # No journal files were found.68solo # No journal boot entry found for the specified boot (+0).69solo # No journal files were found.70solo # No journal boot entry found for the specified boot (+0).71solo # No journal files were found.72solo # No journal boot entry found for the specified boot (+0).73solo # No journal files were found.74solo # No journal boot entry found for the specified boot (+0).75solo # No journal files were found.76solo # No journal boot entry found for the specified boot (+0).77solo: still waiting for container 'solo' to reach ready state...78solo # [325201.247130] solo systemd-journald[58]: Journal started79solo # [325201.247491] solo systemd-journald[58]: Runtime Journal (/run/log/journal/98c23515e10947079fc030ca32dbeef8) is 8M, max 4G, 3.9G free.80solo # [325201.617647] solo systemd[1]: Finished Apply Kernel Variables.81solo # [325201.630656] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.82solo # [325201.645989] solo systemd[1]: Starting Flush Journal to Persistent Storage...83solo # [325201.647542] solo systemd[1]: Starting Create Static Device Nodes in /dev...84solo # [325201.756242] solo systemd-journald[58]: Time spent on flushing to /var/log/journal/98c23515e10947079fc030ca32dbeef8 is 2.897ms for 6 entries.85solo # [325201.756242] solo systemd-journald[58]: System Journal (/var/log/journal/98c23515e10947079fc030ca32dbeef8) is 512B, max 4G, 3.9G free.86solo # [325201.759664] solo systemd[1]: Finished Firewall.87solo # [325201.762602] solo systemd[1]: Finished Create Static Device Nodes in /dev.88solo # [325201.763444] solo systemd[1]: Reached target Preparation for Local File Systems.89solo # [325201.763586] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys90solo # [325201.769899] solo systemd[1]: Finished Flush Journal to Persistent Storage.91solo # [325202.235089] solo systemd[1]: Mounting /run/wrappers...92solo # [325202.479692] solo systemd[1]: Mounted /run/wrappers.93solo # [325202.481657] solo systemd[1]: Reached target Local File Systems.94solo # [325202.482968] solo systemd[1]: Listening on Boot Loader Control Service Socket.95solo # [325202.484714] solo systemd[1]: Starting Create SUID/SGID Wrappers...96solo # [325202.485084] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container97solo # [325202.487665] solo systemd[1]: Starting Save Transient machine-id to Disk...98solo # [325202.488670] solo systemd[1]: Starting Create System Files and Directories...99solo # [325202.511866] solo systemd-tmpfiles[162]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted100solo # [325202.513028] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal failed: Operation not permitted101solo # [325202.513262] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal/98c23515e10947079fc030ca32dbeef8 failed: Operation not permitted102solo # [325202.513522] solo systemd-tmpfiles[162]: fchmod() of /run/log/journal failed: Operation not permitted103solo # [325202.516947] solo systemd[1]: Finished Create System Files and Directories.104solo # [325202.524509] solo suid-sgid-wrappers-start[170]: chmod: changing permissions of '/run/wrappers/wrappers.dpHpziAKju/chsh': Operation not permitted105solo # [325202.536755] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE106solo # [325202.537101] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available107solo # [325202.537150] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available108solo # [325202.537177] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.109solo # [325202.537706] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.110solo # [325202.542923] solo systemd[1]: Starting Rebuild Journal Catalog...111solo # [325202.545093] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...112solo # [325202.581367] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.113solo # [325202.582768] solo systemd[1]: Finished Save Transient machine-id to Disk.114solo # [325202.583092] solo systemd[1]: Finished Rebuild Journal Catalog.115solo # [325202.589004] solo systemd[1]: Starting Update is Completed...116solo # [325202.589436] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.117solo # [325202.605772] solo systemd[1]: Finished Update is Completed.118solo # [325202.605920] solo systemd[1]: Reached target System Initialization.119solo # [325202.606033] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container120solo # [325202.606346] solo systemd[1]: Started Daily Cleanup of Temporary Directories.121solo # [325202.606370] solo systemd[1]: Reached target Timer Units.122solo # [325202.606529] solo systemd[1]: Listening on D-Bus System Message Bus Socket.123solo # [325202.607676] solo systemd[1]: Listening on Nix Daemon Socket.124solo # [325202.607860] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.125solo # [325202.607882] solo systemd[1]: Reached target Socket Units.126solo # [325202.607926] solo systemd[1]: Reached target Basic System.127solo # [325202.610699] solo systemd[1]: Starting Import lastlog data into lastlog2 database...128solo # [325202.613211] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...129solo # [325202.615040] solo systemd[1]: Starting resolvconf update...130solo # [325202.616469] solo systemd[1]: Starting Tinc Daemon - mesh...131solo # [325202.641532] solo tinc.mesh-pre-start[188]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.132solo # [325202.644621] solo systemd[1]: Started Tinc Daemon - mesh.133solo # [325202.645082] solo systemd[1]: Finished Import lastlog data into lastlog2 database.134solo # [325202.649138] solo systemd[1]: Started tinc-auth.service.135solo # [325202.661312] solo tincd[190]: [INFO tincd] tincd 0.1.0 starting, debug level 0136solo # [325202.662132] solo tincd[190]: [INFO tincd] tincd starting, name=alpha137solo # [325202.662163] solo tincd[190]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!138solo # [325202.662348] solo tincd[190]: [INFO tincd] Device mode: Tun, interface: dummy139solo # [325202.662701] solo tincd[190]: [INFO tincd::net] Listening on 0.0.0.0:655140solo # [325202.662732] solo tincd[190]: [INFO tincd::net] Listening on [::]:655141solo # [325202.663728] solo tincd[190]: [INFO tincd] Ready142solo # [325202.742017] solo tinc-auth[192]: tinc-auth: IdP listening on 127.0.0.1:8443143solo # [325203.480562] solo tinc-auth[192]: tinc-auth: listening (net=mesh)144solo # [325203.491177] solo systemd[1]: nscd.service: Failed to read pids.max for control group /system.slice/nscd.service, ignoring: No data available145solo # [325203.491217] solo systemd[1]: nscd.service: Deactivated successfully.146solo # [325203.491503] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).147solo # [325203.495966] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...148solo # [325203.508384] solo systemd[1]: Finished resolvconf update.149solo # [325203.508525] solo systemd[1]: Reached target Preparation for Network.150solo # [325203.509905] solo systemd[1]: Starting Address configuration of eth1...151solo # [325203.511325] solo systemd[1]: Starting Extra networking commands....152solo # [325203.546720] solo network-addresses-eth1-start[260]: adding address 192.168.1.1/24... done153solo # [325203.551128] solo network-addresses-eth1-start[260]: adding address 2001:db8:1::1/64... done154solo # [325203.558006] solo systemd[1]: Finished Address configuration of eth1.155solo # [325204.528689] solo systemd[1]: Finished Extra networking commands..156solo # [325204.528883] solo systemd[1]: Reached target Network.157solo # [325204.590125] solo systemd[1]: Started Name Service Cache Daemon (nsncd).158solo # [325204.590209] solo systemd[1]: Reached target Host and Network Name Lookups.159solo # [325204.590275] solo systemd[1]: Reached target User and Group Name Lookups.160solo # [325204.680970] solo systemd[1]: Starting User Login Management...161solo # [325204.682437] solo systemd[1]: Starting Permit User Sessions...162solo # [325204.695990] solo systemd[1]: Finished Permit User Sessions.163solo # [325204.698062] solo systemd[1]: Started Console Getty.164solo # [325204.698111] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0165solo # [325204.698131] solo systemd[1]: Reached target Login Prompts.166solo # [325207.187645] solo systemd-logind[323]: New seat seat0.167solo # [325207.188509] solo systemd[1]: Starting D-Bus System Message Bus...168solo # [325207.188815] solo systemd[1]: Started User Login Management.169solo # [325207.191222] solo systemd[1]: Starting linger-users.service...170solo # [325207.752075] solo nsncd[253]: Nov 11 10:24:07.050 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"171solo # [325207.756064] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available172solo # [325207.756118] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available173solo # [325207.756155] solo systemd[1]: linger-users.service: Deactivated successfully.174solo # [325207.756511] solo systemd[1]: Finished linger-users.service.175solo # [325207.756749] solo systemd[1]: Reached target Multi-User System.176solo # [325208.139737] solo dbus-broker-launch[336]: Looking up NSS user entry for 'systemd-timesync'...177solo # [325208.145767] solo dbus-broker-launch[336]: NSS returned no entry for 'systemd-timesync'178solo # [325208.145767] solo dbus-broker-launch[336]: Invalid user-name in /nix/store/j162pn4f71imwb1qyzqwd6w9bzv8b65z-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"179solo # [325208.148415] solo systemd[1]: Started D-Bus System Message Bus.180solo # [325208.148815] solo systemd[1]: Startup finished in 21.805s.181solo # [325208.166451] solo dbus-broker-launch[336]: Ready182solo: (finished: waiting for unit tinc.mesh.service, in 37.09 seconds)183solo: waiting for unit tinc-auth.service184solo: (finished: waiting for unit tinc-auth.service, in 1.39 seconds)185solo: waiting for TCP port 8443 on localhost186Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!187solo: (finished: waiting for TCP port 8443 on localhost, in 1.58 seconds)188solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration189solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.05 seconds)190solo: 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'191solo: (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)192solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=lOzc5-fH-yysOoEfrfmI9Gd_R1qZi-ubhs0DQ3x3LEU -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil193solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=lOzc5-fH-yysOoEfrfmI9Gd_R1qZi-ubhs0DQ3x3LEU -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.03 seconds)194solo: must succeed: curl -fsS -H 'Authorization: Bearer ao5GImhBM7o5ib1rZY-jQqK6cGj754gvZIksbU0nr_M' http://127.0.0.1:8443/userinfo195solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer ao5GImhBM7o5ib1rZY-jQqK6cGj754gvZIksbU0nr_M' http://127.0.0.1:8443/userinfo, in 3.76 seconds)196(finished: run the VM test script, in 45.48 seconds)197test script finished in 47.11s198cleanup199kill NspawnMachine (pid 50)200(finished: cleanup, in 0.62 seconds)201additionally exposed symbols:202 solo,203 vlan1,204 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_ssh205Container solo terminated by signal KILL.