nixbot

builds

succeeded container-test-run-tinc-auth-container checks.x86_64-linux.nixos-tinc-auth-container · build #74 · raw

1Machine state will be reset. To keep it, pass --keep-machine-state2start all VLans3(finished: start all VLans, in 0.04 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.01 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 # [10886991.774832] solo systemd-journald[54]: Journal started35solo # [10886991.774914] solo systemd-journald[54]: Runtime Journal (/run/log/journal/f0da839531c54e309875bc45801ee179) is 8M, max 2.5G, 2.5G free.36solo # [10886991.905540] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.37solo # [10886992.053535] solo systemd[1]: Starting Flush Journal to Persistent Storage...38solo # [10886992.066383] solo systemd[1]: Starting Create Static Device Nodes in /dev...39solo # [10886992.213464] solo systemd-journald[54]: Time spent on flushing to /var/log/journal/f0da839531c54e309875bc45801ee179 is 6.355ms for 5 entries.40solo # [10886992.213464] solo systemd-journald[54]: System Journal (/var/log/journal/f0da839531c54e309875bc45801ee179) is 512B, max 4G, 3.9G free.41solo # [10886992.268710] solo systemd[1]: Finished Flush Journal to Persistent Storage.42solo # [10886992.291069] solo systemd[1]: Finished Create Static Device Nodes in /dev.43solo # [10886992.292672] solo systemd[1]: Reached target Preparation for Local File Systems.44solo # [10886992.292847] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys45solo # [10886992.489747] solo systemd[1]: Mounting /run/wrappers...46solo # [10886993.091689] solo systemd[1]: Mounted /run/wrappers.47solo # [10886993.092715] solo systemd[1]: Reached target Local File Systems.48solo # [10886993.107216] solo systemd[1]: Listening on Boot Loader Control Service Socket.49solo # [10886993.114241] solo systemd[1]: Starting Create SUID/SGID Wrappers...50solo # [10886993.114298] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container51solo # [10886993.122678] solo systemd[1]: Starting Save Transient machine-id to Disk...52solo # [10886993.140217] solo systemd[1]: Starting Create System Files and Directories...53solo # [10886993.187640] solo systemd-tmpfiles[133]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted54solo # [10886993.187902] solo systemd-tmpfiles[133]: fchmod() of /var/log/journal failed: Operation not permitted55solo # [10886993.188078] solo systemd-tmpfiles[133]: fchmod() of /var/log/journal/f0da839531c54e309875bc45801ee179 failed: Operation not permitted56solo # [10886993.188317] solo systemd-tmpfiles[133]: fchmod() of /run/log/journal failed: Operation not permitted57solo # [10886993.633689] solo systemd[1]: Finished Create System Files and Directories.58solo # [10886993.804157] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.59solo # [10886993.805896] solo systemd[1]: Finished Save Transient machine-id to Disk.60solo # [10886993.834285] solo systemd[1]: Starting Rebuild Journal Catalog...61solo # [10886993.859990] solo suid-sgid-wrappers-start[157]: chmod: changing permissions of '/run/wrappers/wrappers.JTuIDCkpkX/chsh': Operation not permitted62solo # [10886993.865270] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...63solo # [10886993.865597] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE64solo # [10886993.865716] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.65solo # [10886993.865915] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.66solo # [10886993.917630] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.67solo # [10886994.002250] solo systemd[1]: Finished Firewall.68solo # [10886994.131896] solo systemd[1]: Finished Rebuild Journal Catalog.69solo # [10886994.139876] solo systemd[1]: Starting Update is Completed...70solo: still waiting for container 'solo' to reach ready state...71solo # [10886994.777611] solo systemd[1]: Finished Update is Completed.72solo # [10886994.778530] solo systemd[1]: Reached target System Initialization.73solo # [10886994.780595] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container74solo # [10886994.780677] solo systemd[1]: Started Daily Cleanup of Temporary Directories.75solo # [10886994.780717] solo systemd[1]: Reached target Timer Units.76solo # [10886994.780928] solo systemd[1]: Listening on D-Bus System Message Bus Socket.77solo # [10886994.781205] solo systemd[1]: Listening on Nix Daemon Socket.78solo # [10886994.781368] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.79solo # [10886994.781392] solo systemd[1]: Reached target Socket Units.80solo # [10886994.781438] solo systemd[1]: Reached target Basic System.81solo # [10886994.827495] solo systemd[1]: Starting Import lastlog data into lastlog2 database...82solo # [10886994.830895] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...83solo # [10886994.840610] solo systemd[1]: Starting resolvconf update...84solo # [10886994.936102] solo systemd[1]: Starting Tinc Daemon - mesh...85solo # [10886995.441957] solo tinc.mesh-pre-start[205]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.86solo # [10886995.459908] solo systemd[1]: Started Tinc Daemon - mesh.87solo # [10886995.467773] solo systemd[1]: Started tinc-auth.service.88solo # [10886995.468292] solo systemd[1]: Finished Import lastlog data into lastlog2 database.89solo # [10886995.508397] solo tincd[208]: [INFO tincd] tincd 0.1.0 starting, debug level 090solo # [10886995.512311] solo tincd[208]: [INFO tincd] tincd starting, name=alpha91solo # [10886995.512311] solo tincd[208]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!92solo # [10886995.512311] solo tincd[208]: [INFO tincd] Device mode: Tun, interface: dummy93solo # [10886995.512311] solo tincd[208]: [INFO tincd::net] Listening on 0.0.0.0:65594solo # [10886995.512311] solo tincd[208]: [INFO tincd::net] Listening on [::]:65595solo # [10886995.512311] solo tincd[208]: [INFO tincd] Ready96solo # [10886995.622475] solo tinc-auth[210]: tinc-auth: IdP listening on 127.0.0.1:844397solo # [10886995.622475] solo tinc-auth[210]: tinc-auth: listening (net=mesh)98solo # [10886995.657495] solo systemd[1]: nscd.service: Deactivated successfully.99solo # [10886995.659114] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).100solo # [10886995.690068] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...101solo # [10886995.969017] solo resolvconf-start[246]: setfacl: /run/resolvconf: Operation not supported102solo # [10886995.994578] solo systemd[1]: resolvconf.service: Main process exited, code=exited, status=1/FAILURE103solo # [10886995.994722] solo systemd[1]: resolvconf.service: Failed with result 'exit-code'.104solo # [10886995.995385] solo systemd[1]: Failed to start resolvconf update.105solo # [10886995.995662] solo systemd[1]: Reached target Preparation for Network.106solo # [10886996.013392] solo systemd[1]: Starting Address configuration of eth1...107solo # [10886996.046178] solo systemd[1]: Starting Extra networking commands....108solo # [10886996.255600] solo network-addresses-eth1-start[248]: adding address 192.168.1.1/24... done109solo # [10886996.276070] solo network-addresses-eth1-start[248]: adding address 2001:db8:1::1/64... done110solo # [10886996.322936] solo systemd[1]: Finished Address configuration of eth1.111solo # [10886996.874241] solo systemd[1]: Finished Extra networking commands..112solo # [10886996.875178] solo systemd[1]: Reached target Network.113solo # [10886997.133150] solo nsncd[238]: Aug 30 21:22:23.702 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"114solo # [10886997.129230] solo systemd[1]: Started Name Service Cache Daemon (nsncd).115solo # [10886997.129490] solo systemd[1]: Reached target Host and Network Name Lookups.116solo # [10886997.129562] solo systemd[1]: Reached target User and Group Name Lookups.117solo # [10886997.137300] solo systemd[1]: Starting User Login Management...118solo # [10886997.152330] solo systemd[1]: Starting Permit User Sessions...119solo # [10886997.376231] solo systemd[1]: Finished Permit User Sessions.120solo # [10886997.386962] solo systemd[1]: Started Console Getty.121solo # [10886997.387048] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0122solo # [10886997.387078] solo systemd[1]: Reached target Login Prompts.123solo # [10887003.249752] solo systemd-logind[316]: New seat seat0.124solo # [10887003.250513] solo systemd[1]: Started User Login Management.125solo # [10887003.288221] solo systemd[1]: Starting D-Bus System Message Bus...126solo # [10887003.310183] solo systemd[1]: Starting linger-users.service...127solo # [10887003.683385] solo systemd[1]: linger-users.service: Deactivated successfully.128solo # [10887003.683892] solo systemd[1]: Finished linger-users.service.129solo # [10887003.684072] solo systemd[1]: Reached target Multi-User System.130solo: still waiting for container 'solo' to reach ready state...131solo: (finished: waiting for unit tinc.mesh.service, in 22.38 seconds)132solo: waiting for unit tinc-auth.service133solo: (finished: waiting for unit tinc-auth.service, in 0.16 seconds)134solo: waiting for TCP port 8443 on localhost135solo # [10887006.510085] solo dbus-broker-launch[326]: Looking up NSS user entry for 'systemd-timesync'...136solo # [10887006.512015] solo dbus-broker-launch[326]: NSS returned no entry for 'systemd-timesync'137solo # [10887006.512015] solo dbus-broker-launch[326]: Invalid user-name in /nix/store/m3nbj2hjbwvb8z3ggp44ng6v8b2v5si6-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"138solo # [10887006.515472] solo systemd[1]: Started D-Bus System Message Bus.139solo # [10887006.529903] solo dbus-broker-launch[326]: Ready140solo # [10887006.535091] solo systemd[1]: Startup finished in 19.139s.141Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!142solo: (finished: waiting for TCP port 8443 on localhost, in 0.35 seconds)143solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration144solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.18 seconds)145solo: 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'146solo: (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.36 seconds)147solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=EZ16W4oleqmsEIL5DFxc1cnwzJcwEYFcuNJh3ugL-e4 -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil148solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=EZ16W4oleqmsEIL5DFxc1cnwzJcwEYFcuNJh3ugL-e4 -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.06 seconds)149solo: must succeed: curl -fsS -H 'Authorization: Bearer w5QEVjK5xqxolIjHX2IR5tkeHmR4qYlwwjopOguLm2U' http://127.0.0.1:8443/userinfo150solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer w5QEVjK5xqxolIjHX2IR5tkeHmR4qYlwwjopOguLm2U' http://127.0.0.1:8443/userinfo, in 0.06 seconds)151(finished: run the VM test script, in 23.61 seconds)152test script finished in 24.65s153cleanup154kill NspawnMachine (pid 51)155Container solo terminated by signal KILL.156(finished: cleanup, in 0.53 seconds)