Test/worker-executor: make sure that the port is opened in firewall

It turned out that our new F41 CI images have firewalld installed. Make sure that the worker-executor port is opened in firewall, otherwise the worker can't connect to the executor. Signed-off-by: Tomáš Hozza <[email protected]>
osbuild · Jan 27, 2025 · 1b1c474 · 1b1c474
1 parent 1aa363a
commit 1b1c474
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/test/cases/worker-executor.sh b/test/cases/worker-executor.sh
@@ -151,8 +151,12 @@ subprocessPIDs+=( $! )
 ssh -oStrictHostKeyChecking=no -i "$KEYPAIR" "fedora@$EXECUTOR_IP" sudo dnf install -y osbuild-composer osbuild
 
 # no internet access during the build
+# TODO [thozza]: while debugging the test case, it turned out that the worker executor instance in fact has Internet access!
 $AWS_CMD ec2 revoke-security-group-egress --group-id "$SGID" --security-group-rule-ids "$SGRULEID"
 
+# Open incoming port for the worker executor in firewall
+ssh -oStrictHostKeyChecking=no -i "$KEYPAIR" "fedora@$EXECUTOR_IP" sudo firewall-cmd --zone=public --add-port=8001/tcp --permanent || true
+
 ssh -oStrictHostKeyChecking=no -i "$KEYPAIR" "fedora@$EXECUTOR_IP" sudo /usr/libexec/osbuild-composer/osbuild-worker-executor -host 0.0.0.0 &
 subprocessPIDs+=( $! )