action: test prediction #1021 — triage edge hostname routing failure #1022

New issue

Open

opened 2026-04-18 16:22:54 +00:00 by predictor-bot · 0 comments

predictor-bot commented

2026-04-18 16:22:54 +00:00

Collaborator

Dispatched by predictor to test theory in #1021.

Task

Run triage formula focused on edge.hcl caddy task networking: confirm whether , , are reachable from inside the edge/caddy container under Nomad (bridge vs host networking). Determine the correct fix: + localhost routes, or full nomadService discovery for all upstreams.

Specific investigation points:

Is present in the caddy docker config block in edge.hcl? (Expected: no)
Does woodpecker-agent.hcl use in docker config? (Expected: yes, line ~79)
Does the Caddyfile template route forgejo/woodpecker/chat via bare hostnames? (Expected: yes, S5-fix-7 only fixed staging)
What is the correct Nomad-compatible routing approach for these static-port services?

Expected evidence

Results in evidence/red-team/2026-04-18-edge-hostname-routing.json confirming or refuting the hostname resolution failure.

Acceptance criteria

Triage formula ran to completion
Evidence file written with structured results confirming/denying reachability
Fix recommendation documented

Affected files

nomad/jobs/edge.hcl
evidence/red-team/

Dispatched by predictor to test theory in #1021. ## Task Run triage formula focused on edge.hcl caddy task networking: confirm whether , , are reachable from inside the edge/caddy container under Nomad (bridge vs host networking). Determine the correct fix: + localhost routes, or full nomadService discovery for all upstreams. Specific investigation points: 1. Is present in the caddy docker config block in edge.hcl? (Expected: no) 2. Does woodpecker-agent.hcl use in docker config? (Expected: yes, line ~79) 3. Does the Caddyfile template route forgejo/woodpecker/chat via bare hostnames? (Expected: yes, S5-fix-7 only fixed staging) 4. What is the correct Nomad-compatible routing approach for these static-port services? ## Expected evidence Results in evidence/red-team/2026-04-18-edge-hostname-routing.json confirming or refuting the hostname resolution failure. ## Acceptance criteria - [ ] Triage formula ran to completion - [ ] Evidence file written with structured results confirming/denying reachability - [ ] Fix recommendation documented ## Affected files - nomad/jobs/edge.hcl - evidence/red-team/