container-test-run-tinc-auth-container
checks.x86_64-linux.nixos-tinc-auth-container
· build #79
· raw
1Machine state will be reset. To keep it, pass --keep-machine-state2start all VLans3(finished: start all VLans, in 0.05 seconds)4Initializing machine ID from random generator.5Test will time out and terminate in 3600.0 seconds6run the VM test script7additionally exposed symbols:8 solo,9 vlan1,10 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_ssh11start all VMs12solo: systemd-nspawn running (pid 51)13solo: Waiting for journal at /build/vm-state-solo/var/log/journal...14(finished: start all VMs, in 0.18 seconds)15solo: waiting for unit tinc.mesh.service16nixos-nspawn(solo): TAP vde-tap1 not found; container will be isolated from VDE17nixos-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.18Note: 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.19░ Spawning container solo on /build/vm-state-solo.20solo # No journal files were found.21solo # No journal boot entry found for the specified boot (+0).22solo # No journal files were found.23solo # No journal boot entry found for the specified boot (+0).24solo # No journal files were found.25solo # No journal boot entry found for the specified boot (+0).26solo # No journal files were found.27solo # No journal boot entry found for the specified boot (+0).28solo # No journal files were found.29solo # No journal boot entry found for the specified boot (+0).30solo # No journal files were found.31solo # No journal boot entry found for the specified boot (+0).32solo # No journal files were found.33solo # No journal boot entry found for the specified boot (+0).34solo # No journal files were found.35solo # No journal boot entry found for the specified boot (+0).36solo: still waiting for container 'solo' to reach ready state...37solo # [11052580.240835] solo systemd-journald[54]: Journal started38solo # [11052580.240971] solo systemd-journald[54]: Runtime Journal (/run/log/journal/4640f300ff0f4de9b00d0dcab9bbdb42) is 8M, max 2.5G, 2.5G free.39solo # [11052580.325531] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.40solo # [11052580.408990] solo systemd[1]: Starting Flush Journal to Persistent Storage...41solo # [11052580.411247] solo systemd[1]: Starting Create Static Device Nodes in /dev...42solo # [11052580.637732] solo systemd-journald[54]: Time spent on flushing to /var/log/journal/4640f300ff0f4de9b00d0dcab9bbdb42 is 8.185ms for 5 entries.43solo # [11052580.637732] solo systemd-journald[54]: System Journal (/var/log/journal/4640f300ff0f4de9b00d0dcab9bbdb42) is 512B, max 4G, 3.9G free.44solo # [11052580.671765] solo systemd[1]: Finished Flush Journal to Persistent Storage.45solo # [11052580.874422] solo systemd[1]: Finished Create Static Device Nodes in /dev.46solo # [11052580.874897] solo systemd[1]: Reached target Preparation for Local File Systems.47solo # [11052580.875051] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys48solo # [11052581.024082] solo systemd[1]: Mounting /run/wrappers...49solo # [11052581.214897] solo systemd[1]: Mounted /run/wrappers.50solo # [11052581.325515] solo systemd[1]: Reached target Local File Systems.51solo # [11052581.326962] solo systemd[1]: Listening on Boot Loader Control Service Socket.52solo # [11052581.436776] solo systemd[1]: Starting Create SUID/SGID Wrappers...53solo # [11052581.436852] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container54solo # [11052581.443407] solo systemd[1]: Starting Save Transient machine-id to Disk...55solo # [11052581.447142] solo systemd[1]: Starting Create System Files and Directories...56solo # [11052581.623654] solo suid-sgid-wrappers-start[119]: chmod: changing permissions of '/run/wrappers/wrappers.CiXnRSix6N/chsh': Operation not permitted57solo # [11052581.807805] solo systemd-tmpfiles[111]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted58solo # [11052581.808134] solo systemd-tmpfiles[111]: fchmod() of /var/log/journal failed: Operation not permitted59solo # [11052581.808311] solo systemd-tmpfiles[111]: fchmod() of /var/log/journal/4640f300ff0f4de9b00d0dcab9bbdb42 failed: Operation not permitted60solo # [11052581.808549] solo systemd-tmpfiles[111]: fchmod() of /run/log/journal failed: Operation not permitted61solo # [11052583.513505] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.62solo # [11052583.885749] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE63solo # [11052583.885876] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.64solo # [11052583.892114] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.65solo # [11052583.906291] solo systemd[1]: Finished Save Transient machine-id to Disk.66solo # [11052583.926895] solo systemd[1]: Finished Create System Files and Directories.67solo # [11052584.130178] solo systemd[1]: Starting Rebuild Journal Catalog...68solo # [11052584.135883] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...69solo # [11052584.371528] solo systemd[1]: Finished Firewall.70solo # [11052584.499353] solo systemd[1]: Finished Rebuild Journal Catalog.71solo # [11052584.573032] solo systemd[1]: Starting Update is Completed...72solo # [11052584.585117] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.73solo # [11052584.758387] solo systemd[1]: Finished Update is Completed.74solo # [11052584.758869] solo systemd[1]: Reached target System Initialization.75solo # [11052584.761025] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container76solo # [11052584.761135] solo systemd[1]: Started Daily Cleanup of Temporary Directories.77solo # [11052584.761179] solo systemd[1]: Reached target Timer Units.78solo # [11052584.761376] solo systemd[1]: Listening on D-Bus System Message Bus Socket.79solo # [11052584.761632] solo systemd[1]: Listening on Nix Daemon Socket.80solo # [11052584.761808] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.81solo # [11052584.761836] solo systemd[1]: Reached target Socket Units.82solo # [11052584.761882] solo systemd[1]: Reached target Basic System.83solo # [11052584.850042] solo systemd[1]: Starting Import lastlog data into lastlog2 database...84solo # [11052584.871197] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...85solo # [11052584.906344] solo systemd[1]: Starting resolvconf update...86solo # [11052584.909126] solo systemd[1]: Starting Tinc Daemon - mesh...87solo # [11052585.150429] solo systemd[1]: Finished Import lastlog data into lastlog2 database.88solo # [11052585.347454] solo nsncd[176]: Sep 01 19:22:11.920 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"89solo # [11052585.352620] solo systemd[1]: Started Name Service Cache Daemon (nsncd).90solo # [11052585.352722] solo systemd[1]: Reached target Host and Network Name Lookups.91solo # [11052585.352791] solo systemd[1]: Reached target User and Group Name Lookups.92solo # [11052585.370640] solo systemd[1]: Starting User Login Management...93solo # [11052585.596093] solo tinc.mesh-pre-start[211]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.94solo # [11052585.918280] solo systemd[1]: Started Tinc Daemon - mesh.95solo # [11052585.924280] solo systemd[1]: Started tinc-auth.service.96solo # [11052586.127385] solo tinc-auth[223]: tinc-auth: refusing to serve the IdP: cannot verify 127.0.0.1 against tincd: Could not open pid file /run/tinc.mesh.pid: No such file or directory (os error 2)97solo # [11052586.129276] solo systemd[1]: tinc-auth.service: Main process exited, code=exited, status=1/FAILURE98solo # [11052586.129425] solo systemd[1]: tinc-auth.service: Failed with result 'exit-code'.99solo # [11052586.268234] solo tincd[221]: [INFO tincd] tincd 0.1.0 starting, debug level 0100solo # [11052586.268747] solo tincd[221]: [INFO tincd] tincd starting, name=alpha101solo # [11052586.268747] solo tincd[221]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!102solo # [11052586.268865] solo tincd[221]: [INFO tincd] Device mode: Tun, interface: dummy103solo # [11052586.272081] solo tincd[221]: [INFO tincd::net] Listening on 0.0.0.0:655104solo # [11052586.272081] solo tincd[221]: [INFO tincd::net] Listening on [::]:655105solo # [11052586.272081] solo tincd[221]: [INFO tincd] Ready106solo # [11052586.626721] solo systemd[1]: Stopped target Host and Network Name Lookups.107solo # [11052586.626797] solo systemd[1]: Stopping Host and Network Name Lookups...108solo # [11052586.626849] solo systemd[1]: Stopped target User and Group Name Lookups.109solo # [11052586.626882] solo systemd[1]: Stopping User and Group Name Lookups...110solo # [11052586.627098] solo systemd[1]: Stopping Name Service Cache Daemon (nsncd)...111solo # [11052586.845563] solo systemd[1]: nscd.service: Deactivated successfully.112solo # [11052586.845844] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).113solo # [11052586.874948] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...114solo # [11052587.233595] solo systemd[1]: tinc-auth.service: Scheduled restart job, restart counter is at 1.115solo # [11052587.238455] solo systemd[1]: Started tinc-auth.service.116solo # [11052587.270030] solo resolvconf-start[259]: setfacl: /run/resolvconf: Operation not supported117solo # [11052587.374310] solo systemd[1]: resolvconf.service: Main process exited, code=exited, status=1/FAILURE118solo # [11052587.374451] solo systemd[1]: resolvconf.service: Failed with result 'exit-code'.119solo # [11052587.375022] solo systemd[1]: Failed to start resolvconf update.120solo # [11052587.376047] solo systemd[1]: Reached target Preparation for Network.121solo # [11052587.499470] solo systemd[1]: Starting Address configuration of eth1...122solo # [11052587.516315] solo tinc-auth[258]: tinc-auth: IdP listening on 127.0.0.1:8443123solo # [11052587.516315] solo tinc-auth[258]: tinc-auth: listening (net=mesh)124solo # [11052587.598201] solo systemd[1]: Starting Extra networking commands....125solo # [11052587.882325] solo nsncd[249]: Sep 01 19:22:14.454 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"126solo # [11052587.892296] solo systemd[1]: Started Name Service Cache Daemon (nsncd).127solo # [11052587.892451] solo systemd[1]: Reached target Host and Network Name Lookups.128solo # [11052587.892537] solo systemd[1]: Reached target User and Group Name Lookups.129solo # [11052588.502554] solo network-addresses-eth1-start[261]: adding address 192.168.1.1/24... done130solo # [11052588.535031] solo network-addresses-eth1-start[261]: adding address 2001:db8:1::1/64... done131solo # [11052588.612115] solo systemd[1]: Finished Address configuration of eth1.132solo # [11052589.387887] solo systemd[1]: Finished Extra networking commands..133solo # [11052589.388985] solo systemd[1]: Reached target Network.134solo # [11052589.393558] solo systemd[1]: Starting Permit User Sessions...135solo # [11052589.678147] solo systemd[1]: Finished Permit User Sessions.136solo # [11052589.697199] solo systemd[1]: Started Console Getty.137solo # [11052589.697280] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0138solo # [11052589.697309] solo systemd[1]: Reached target Login Prompts.139solo: still waiting for container 'solo' to reach ready state...140solo # [11052593.347452] solo systemd-logind[195]: New seat seat0.141solo # [11052593.364212] solo systemd[1]: Starting D-Bus System Message Bus...142solo # [11052593.368198] solo systemd[1]: Started User Login Management.143solo # [11052593.391316] solo systemd[1]: Starting linger-users.service...144solo # [11052593.596576] solo systemd[1]: linger-users.service: Deactivated successfully.145solo # [11052593.596910] solo systemd[1]: Finished linger-users.service.146solo # [11052593.597115] solo systemd[1]: Reached target Multi-User System.147solo # [11052597.673636] solo dbus-broker-launch[338]: Looking up NSS user entry for 'systemd-timesync'...148solo # [11052597.684315] solo dbus-broker-launch[338]: NSS returned no entry for 'systemd-timesync'149solo # [11052597.684315] solo dbus-broker-launch[338]: Invalid user-name in /nix/store/vj9fr0shj6yfmxi9ab22r2pqc7f4vg7z-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"150solo # [11052597.687221] solo systemd[1]: Started D-Bus System Message Bus.151solo # [11052597.687967] solo systemd[1]: Startup finished in 20.446s.152solo # [11052597.877507] solo dbus-broker-launch[338]: Ready153solo: (finished: waiting for unit tinc.mesh.service, in 28.10 seconds)154solo: waiting for unit tinc-auth.service155solo: (finished: waiting for unit tinc-auth.service, in 0.09 seconds)156solo: waiting for TCP port 8443 on localhost157Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!158solo: (finished: waiting for TCP port 8443 on localhost, in 0.29 seconds)159solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration160solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.37 seconds)161solo: 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'162solo: (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.27 seconds)163solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=sudVjpnXgum1GtBCuiM0j-2KTrfRjoRBDBn-SRmuJFs -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil164solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=sudVjpnXgum1GtBCuiM0j-2KTrfRjoRBDBn-SRmuJFs -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.09 seconds)165solo: must succeed: curl -fsS -H 'Authorization: Bearer ynba_HUBlneVqlxSYWZrt9mzGr1pSGTlzvd9raDtx34' http://127.0.0.1:8443/userinfo166solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer ynba_HUBlneVqlxSYWZrt9mzGr1pSGTlzvd9raDtx34' http://127.0.0.1:8443/userinfo, in 0.41 seconds)167(finished: run the VM test script, in 29.81 seconds)168test script finished in 30.25s169cleanup170kill NspawnMachine (pid 51)171Container solo terminated by signal KILL.172(finished: cleanup, in 0.62 seconds)