tests/multi-server: don't auto-restart kafka-producer1

proto_load on kafka-producer1 runs its generator to completion and then
radiusd exits normally.  With restart: unless-stopped docker would bring
the container straight back up, rerun apt-get install / radiusd startup
(~30s each time), fire a fresh batch of traffic, and race the test
framework's verify phase - the listener file ended up with a mix of
in-flight and post-restart events.

Set restart: "no" so the container exits once and stays exited; the
test completes based on the consumer's summary line.

diff --git a/src/tests/multi-server/environments/kafka.yml.j2 b/src/tests/multi-server/environments/kafka.yml.j2
index bbd524188519a5c0e027b122fdc7ed5e2b1fc859..351581233fc1c1c08f4b7f0e8e860dbc35a2f4a8 100644 (file)
--- a/src/tests/multi-server/environments/kafka.yml.j2
+++ b/src/tests/multi-server/environments/kafka.yml.j2
@@ -78,7 +78,13 @@ services:
     - ${DATA_PATH}/freeradius/kafka-producer1/load-generator-packets/:/etc/raddb/load-generator-packets/
     - ${DATA_PATH}/freeradius/env-setup.sh:/tmp/env-setup.sh
     - ${LISTENER_DIR}/:/var/run/multi-server/
-    restart: unless-stopped
+    #
+    #  proto_load runs the generator to completion and then radiusd
+    #  exits normally.  If docker restarts the container at that point
+    #  the next generator run duplicates traffic and races the test
+    #  framework's verify phase.  Let it exit once and stay exited.
+    #
+    restart: "no"
     environment:
       #
       #  YAML's `<<:` anchor merge doesn't union nested dicts, so