From 675141379067858376698d5f75ab163977d33e3a Mon Sep 17 00:00:00 2001
From: Vika <vika@fireburn.ru>
Date: Wed, 1 Jan 2025 08:24:19 +0300
Subject: distributed-test: wait for Kittybox to start up explicitly

Makes logs more readable, because we aren't confused on concurrency
that the socket listener introduces.

Change-Id: Id471d314a1507b5b48d6fa53ba9ca743977c1c6a
---
 nixos-tests/distributed-test.nix | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/nixos-tests/distributed-test.nix b/nixos-tests/distributed-test.nix
index ee0755f..f44fe96 100644
--- a/nixos-tests/distributed-test.nix
+++ b/nixos-tests/distributed-test.nix
@@ -23,6 +23,7 @@ kittybox:
     systemd.services.kittybox = {
       bindsTo = [ "srv.mount" ];
       after = [ "srv.mount" ];
+      wantedBy = lib.mkForce [ "multi-user.target" ];
       environment.PGPASSWORD = "swordfish";
       serviceConfig = {
         DynamicUser = lib.mkForce false;
@@ -99,7 +100,7 @@ in {
     start_all()
 
     for machine in servants:
-        machine.wait_for_open_port(8080)
+        machine.wait_for_unit("kittybox.service")
 
     # Onboarding
     servants[0].copy_from_host("${./onboarding.json}", "/root/onboarding.json")
-- 
cgit 1.4.1