From cc79ad15e5e6c6af795fe341e92d5212a8a8983b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Hozza?= Date: Mon, 27 Jan 2025 17:09:37 +0100 Subject: [PATCH] Test/worker-executor: make sure that the port is opened in firewall MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- test/cases/worker-executor.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/test/cases/worker-executor.sh b/test/cases/worker-executor.sh index 6ccacd3db..f510102ad 100644 --- a/test/cases/worker-executor.sh +++ b/test/cases/worker-executor.sh @@ -151,8 +151,14 @@ 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" +greenprint "🔥 opening worker-executor port on 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 firewall-cmd --reload || true + +greenprint "🚀 Starting worker executor" ssh -oStrictHostKeyChecking=no -i "$KEYPAIR" "fedora@$EXECUTOR_IP" sudo /usr/libexec/osbuild-composer/osbuild-worker-executor -host 0.0.0.0 & subprocessPIDs+=( $! )