Project

General

Profile

Actions

Bug #16111

closed
PB

Nebula Test nicht erreichbar aus Artemis Test Server Docker Containern

Bug #16111: Nebula Test nicht erreichbar aus Artemis Test Server Docker Containern

Added by Patrick Bassner about 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Major
Assignee:
-
Start date:
06.03.2026
Due date:
% Done:

0%

Estimated time:
SecReporter:
Originally created on:
10.11.2025
Originally updated on:
15.12.2025
Original due date:

Description

Es ist aktuell nicht möglich zu, den Nebula Test Server von den Artemis Containern auf den Testservern zu erreichen (Immediate connect fail for 2a09:80c0:89::1: Network unreachable). Von der Konsole auf der Artemis Test VM selbst klappt es aber auf manchen Servern: TS2, TS3, TS5; nicht auf: TS1, TS4.

Steps to reproduce:
Auf der Artemis Test VM:

{{root@artemis-test-vm5:/home/ga63xiv# docker run --rm --network container:artemis-app-node-1 curlimages/curl:8.10.1 -i }}
{{ -H 'Authorization: ' }}
{{ -H 'Content-Type: application/json' }}
{{ -X POST 'https://test.nebula.artemis.cit.tum.de/transcribe/start' }}
{{ -d '{}'Unable to find image 'curlimages/curl:8.10.1' locally}}
{{8.10.1: Pulling from curlimages/curl}}
{{43c4264eed91: Pull complete}}
{{b68d62cb323c: Pull complete}}
{{4ca545ee6d5d: Pull complete}}
{{Digest: sha256:d9b4541e214bcd85196d6e92e2753ac6d0ea699f0af5741f8c6cccbfcf00ef4b}}
{{Status: Downloaded newer image for curlimages/curl:8.10.1}}
{{ % Total % Received % Xferd Average Speed Time Time Time Current}}
{{ Dload Upload Total Spent Left Speed}}
{{ 0 0 0 0 0 0 0 0 {-}{{-}}:{-}{{-}}:{{-}}{-} 0:01:23 {-}{{-}}:{-}{{-}}:{{-}}{-} 0^C}}
{{got 3 SIGTERM/SIGINTs, forcefully exiting}}

--> Dieser Command hängt / timed out --> Call nicht möglich aus dem Container Netz

Als "Gegenbeispiel" direkt von der Host Konsole:

{{root@artemis-test-vm2:/home/ga63xiv# curl -i -H 'Authorization: ' -H 'Content-Type: application/json' -X POST 'https://test.nebula.artemis.cit.tum.de/transcribe/start' -d '{}'}}
{{HTTP/1.1 401 Unauthorized}}
{{Server: openresty/1.21.4.1}}
{{Date: Mon, 10 Nov 2025 14:21:31 GMT}}
{{Content-Type: text/plain}}
{{Content-Length: 75}}
{{Connection: keep-alive}}
{{{}Strict-Transport-Security: max-age=31536000; includeSubDomains{"error": "Unauthorized - Valid API key required in Authorization header"{}}}} (<-- das ist expected und ok ohne richtigen Key)

--> Funktioniert MEISTENS (–> klappt nicht auf: TS1, TS4)


Related issues 1 (0 open1 closed)

Related to Task #16084: Pyris Test Firewall zu restriktivClosed06.03.2026

Actions

PB Updated by Patrick Bassner about 2 months ago Actions #1

Maybe relates to [https://jira.aet.cit.tum.de/projects/LS1ADMIN/issues/LS1ADMIN-39767?filter=allopenissues]

 

Updated by Anonymous about 2 months ago Actions #2

  • Related to Task #16084: Pyris Test Firewall zu restriktiv added
Actions

Also available in: PDF Atom