Remove E2E failure task doc from Tasks.md

Stale reference to fail2ban/503 health check issue. Task list now starts directly with Setup and Auth.
This commit is contained in:
2026-06-21 11:28:13 +02:00
parent 848531c134
commit 5f33959efd

View File

@@ -1,34 +1,3 @@
# E2E Test Failure Tasks
> Generated from Robot Framework test run on 2026-06-21.
> **Overall Result:** 123 tests, 0 passed, 122 failed, 1 skipped.
> **Root Cause:** Backend health check returns HTTP 503 because fail2ban is not installed/running (`ModuleNotFoundError: No module named 'fail2ban'`). All suites fail at `Suite Setup` → `Wait For Backend Health`.
---
## Task: Fix E2E Suite Setup — Backend Health Check
**Problem:** Every test suite fails during `Suite Setup` because `Wait For Backend Health` in `e2e/resources/common.resource` polls `GET /api/v1/health` and expects HTTP 200. The backend returns HTTP 503 with body `{"status":"unavailable","fail2ban":"offline","database":"ok","scheduler":"running","cache":"initialised"}`.
**Step That Fails:** `Suite Setup``Wait For Backend Health` keyword (line 24 in `common.resource`).
**Files to Check:**
- `e2e/resources/common.resource``Wait For Backend Health` keyword
- `backend/app/routers/health.py` — health endpoint logic
- `backend/app/utils/fail2ban_client.py` — fail2ban module import
- `Docker/compose.debug.yml` — how fail2ban is wired in the Docker stack
**Reference Docs:**
- `e2e/Instructions.md` — "Requires: stack up (make up)"
- `Docs/Deployment.md` — fail2ban dependency setup
- `Makefile``make e2e` target
**Expected Behavior:** Either:
1. The health check accepts 503 as "backend is up but degraded" and proceeds with tests, OR
2. fail2ban is installed and running so health returns 200.
---
## Task: 01 Setup And Auth — Setup Page Renders All Form Fields
**Test:** `Setup Page Renders All Form Fields`
@@ -2279,4 +2248,4 @@
**Reference Docs:**
- `Docs/API-Reference.md` — Setup status endpoint
**Expected Behavior:** `GET /api/v1/setup` returns `{completed: true|false}` indicating whether initial setup has been completed.
**Expected Behavior:** `GET /api/v1/setup` returns `{completed: true|false}` indicating whether initial setup has been completed.