docs(ci): close OIDC run 93 terminal bind RCA and safe cleanup
This commit is contained in:
1 parent
88911c5d68
commit
89bc3f21af
17 files changed
+143
-12
No files matched your search
@@ -48,3 +48,6 @@ Future feature additions need an evidence-backed status update here, an exact de
|
||||
|
||||
|
||||
**P05-OIDC-03-A01 queue audit:** Existing manual [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93), job #206 was **QUEUED** (no start, steps or conclusion). Gitea job log returned `404 job not started`; workflow active with `ubuntu-latest` label, but current runner availability cannot be confirmed. Every real OIDC project/client/user, browser callback/session, negative and mandatory cleanup gate **NOT EXECUTED**; Login security/build acceptance from earlier separate phases remains valid. See `docs/P05-OIDC-03-A01.md`.
|
||||
|
||||
|
||||
**P05-OIDC-03-A02 terminal update:** Gitea [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93) **COMPLETED FAILURE** (job #206 executed) after prior queued status. Four healthy services, portless networking, private Traefik Host route PASS. Socat `SOCKET_BIND_ERROR` and Python fallback `ADDRESS_IN_USE` on private `127.0.0.1:8080` **BLOCKED** further steps; actual listener not identified. Real client/user creation, Chromium Login V2, Auth.js callback/session, negative access and logout **NOT EXECUTED**. Mandatory owned-only cleanup **PASS**. Full authenticated OIDC and production/MFA remain UNVERIFIED.
|
||||
+2
-1
@@ -16,7 +16,8 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | How isolated real OIDC Login V2 browser/session checks work; real CI status/limitations | P05-OIDC-01 / Run #90 BLOCKED before provisioning; cleanup PASS |
|
||||
| [P05-OIDC-02.md](P05-OIDC-02.md) | Pinned prebuilt forwarder, safe private HTTP diagnostics and actual Run #91 evidence | P05-OIDC-02 / real OIDC BLOCKED by forwarder exit 1, cleanup PASS |
|
||||
| [P05-OIDC-03.md](P05-OIDC-03.md) | Same-run socat classification, private Python fallback and exact Gitea status | P05-OIDC-03 / Run #93 QUEUED, no terminal result |
|
||||
| [P05-OIDC-03-A01.md](P05-OIDC-03-A01.md) | Existing Gitea Run #93 read-only scheduling evidence, actual unexecuted checks and safe next steps | P05-OIDC-03-A01 / queue audit, no terminal OIDC acceptance |
|
||||
| [P05-OIDC-03-A01.md](P05-OIDC-03-A01.md) | Historical queue snapshot before Run #93 started; see A02 for terminal state | P05-OIDC-03-A01 / superseded status |
|
||||
| [P05-OIDC-03-A02.md](P05-OIDC-03-A02.md) | Actual terminal Gitea Run #93 port-bind blocker, authentic OIDC test limits, cleanup and next steps | P05-OIDC-03-A02 / completed failure, cleanup PASS |
|
||||
| [SETUP-GUIDE.md](SETUP-GUIDE.md) | Operator/developer prerequisites, configs, activation and safety | DOCS-01 / active; runtime pending |
|
||||
| [FEATURES-STATUS.md](FEATURES-STATUS.md) | Exact implemented/unavailable/unverified feature matrix | DOCS-01 / active |
|
||||
| [TROUBLESHOOTING.md](TROUBLESHOOTING.md) | Known blockers and safe diagnosis based on source status | DOCS-01 / active |
|
||||
|
||||
@@ -24,3 +24,6 @@ Continue inspecting **the existing Run #93**, not dispatching another run. A Git
|
||||
If job #206 begins/completes, inspect its genuine terminal logs and confirm each OIDC, negative-auth and mandatory cleanup marker before declaring acceptance. If it remains queued, record the exact status and missing runner visibility as a **scheduling/availability investigation**, not a proven outage.
|
||||
|
||||
Development evidence and exact phase scope: `notes/P05-OIDC-03-A01.md`. CI source remains at tested candidate `7b80f411b2981e2274d171c12596301ed757b768`; final documentation commit is not a new tested SHA.
|
||||
|
||||
|
||||
**Later terminal correction (P05-OIDC-03-A02):** Run #93 subsequently started and completed **FAILURE**. This A01 file preserves a historical earlier queued snapshot, not the current outcome. The actual job proved backend/private proxy PASS, socat bind error, Python forwarder `ADDRESS_IN_USE`, real OIDC not executed, and complete cleanup PASS. See [P05-OIDC-03-A02.md](P05-OIDC-03-A02.md). No new run was dispatched.
|
||||
@@ -0,0 +1,33 @@
|
||||
# P05-OIDC-03-A02 — Existing Run #93 Final CI Result & Runner Audit
|
||||
|
||||
**Baseline:** `88911c5d685ed4d068e6361d5e920108c217046f`.
|
||||
**Existing [Gitea Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93)**, job **#206**, tested source `7b80f411b2981e2274d171c12596301ed757b768`.
|
||||
**Final status:** **COMPLETED / FAILURE**. The previous “queued” report was accurate at that snapshot but is now superseded by this **later terminal run**.
|
||||
|
||||
## What happened
|
||||
|
||||
The Gitea runner began job #206 at **2026-11-22 18:36:26 UTC** and completed at **18:37:47 UTC**. This proves the runner accepted and executed the job; the exact earlier queue delay is not established. The manual workflow is still **active**, with `runs-on: ubuntu-latest`. Current runner online/busy/label details were not available from the connected Gitea read tool; the actual job did run, so the original “queued” state is **no longer the blocking issue**.
|
||||
|
||||
| Actual Run #93 test | Verified result |
|
||||
| --- | --- |
|
||||
| Git checkout/Docker and Compose | **PASS** |
|
||||
| All 4 disposable ZITADEL/Postgres/Login V2/Traefik services healthy | **PASS** |
|
||||
| No host ports and correct private Traefik Host routing | **PASS** |
|
||||
| Socat prebuilt image/digest | **PASS** |
|
||||
| Socat TCP forwarder | **FAIL** — exited 1; classified `SOCKET_BIND_ERROR` |
|
||||
| Python immutable-image fallback | Image verified and fallback started; TCP bind **FAIL**: `ADDRESS_IN_USE` |
|
||||
| Actual private forwarded 8080 HTTP readiness | **NOT VERIFIED** |
|
||||
| Real OIDC project/client/user creation | **NOT EXECUTED** |
|
||||
| Real Chromium original Login V2 and PKCE/state/nonce/callback | **NOT EXECUTED** |
|
||||
| Auth.js authenticated session, protected page/API, negative cases, logout | **NOT EXECUTED** |
|
||||
| Mandatory owned-only cleanup | **PASS** — verified no run-owned resources left |
|
||||
|
||||
**Root-cause evidence:** In the private proxy network namespace, both forwarders failed to bind TCP port 8080. Python explicitly reported `ADDRESS_IN_USE`. **The exact process occupying port 8080 is not known**; do not assume it is the ZITADEL API, Traefik or another named service without actual listener/process evidence. The original developer Compose and auth source remain unchanged.
|
||||
|
||||
**Safety:** The run-owned container/volume/database/bootstrap/credentials cleanup succeeded: `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS` and `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`. No additional run was dispatched and no production secrets or human accounts were used.
|
||||
|
||||
## Next action
|
||||
|
||||
The appropriate next phase is narrowly scoped CI-only **private port-8080 listener diagnostics and remediation**. On an approved new disposable run, inspect the *actual* listener before binding the forwarder (without logging credentials or network payloads), fix the confirmed collision without exposing host ports or weakening Auth.js, and verify full real client/user/browser/callback/session/negative/cleanup gates. There is **no basis to call real authenticated OIDC PASS today**.
|
||||
|
||||
Exact forensic ledger, scope and source/runner evidence: `notes/P05-OIDC-03-A02.md`. The tested Run #93 source SHA above remains distinct from the later documentation-only Git SHA.
|
||||
@@ -112,3 +112,11 @@ Coolify, HTTPS, secrets, backups, durable storage and focused production readine
|
||||
- **Only existing Run #93** may be checked; no additional dispatch, rerun, cancellation, runner config updates, workflow/backend/Login/Auth.js/CI source edits, local builds or production/real accounts. Exact write scope only `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST and navigation when necessary.
|
||||
- Every Run #93 gate is **NOT EXECUTED**: Git checkout, disposable backend/forwarder/provisioning, browser PKCE/state/nonce/Auth.js callback/session, positive/negative authorization, logout and mandatory owned cleanup. The only correct acceptance statement is **PENDING / NOT VERIFIED**, not test FAILURE or PASS.
|
||||
- Next narrow task: read-only check whether **this same Run #93** is scheduled/completed and inspect authorized Gitea runner online/label/capacity state, without modifying runners or dispatching more jobs. Terminal evidence, if it becomes available, must be documented before claiming positive OIDC acceptance. Evidence: `notes/P05-OIDC-03-A01.md`, operator guidance: `docs/P05-OIDC-03-A01.md`.
|
||||
|
||||
|
||||
## P05-OIDC-03-A02 — Existing Run #93 terminal RCA (APPROVED; 2026-11-23)
|
||||
|
||||
- **Baseline** `88911c5d685ed4d068e6361d5e920108c217046f`. **One existing Run #93**, immutable tested SHA `7b80f411b2981e2274d171c12596301ed757b768`, job #206 eventually scheduled/executed, **overall FAILURE** at 18:37:47 UTC on 2026-11-22. Earlier A01 `queued` snapshot was true then, but is **superseded** by this terminal result. Workflow requests `ubuntu-latest`; current runner online/labels/capacity details still unavailable through connector, but job pickup proved for this run.
|
||||
- **PASS:** checkout and Docker preflight, no host ports, four healthy backend/Postgres/Login V2/Traefik services, direct private proxy Host HTTP 200, pinned image/digests and mandatory owned-only cleanup.
|
||||
- **FAIL:** socat process exited 1, `SOCKET_BIND_ERROR`; same-run Python forwarder exited 1, `ADDRESS_IN_USE` on private TCP `127.0.0.1:8080`. Exact listener identity/port owner **not yet established**. **NOT EXECUTED:** real client/project/human, Chromium original Login V2, PKCE/state/nonce/Auth.js callback/session, protected identity, negatives and logout. Full authenticated OIDC **BLOCKED**.
|
||||
- **Exact A02 write scope only** `notes/**`, `project/**`, relevant `docs/**`, associated README/MINIFEST; all CI/auth/backend/Compose/workflow/runner/source/locks/production strictly **read-only**. No local app tests, second run, tags/releases, real users or production. Evidence `notes/P05-OIDC-03-A02.md`, operator guide `docs/P05-OIDC-03-A02.md`. Next proposed `P05-OIDC-04`: disposable namespace-local port-8080 listener RCA, separately approved narrow CI-only remediation and one fresh isolated full OIDC acceptance.
|
||||
+1
-1
@@ -26,4 +26,4 @@
|
||||
Full update policy is in root [AGENTS.md](../AGENTS.md). A list of available docs is in [MINIFEST.md](MINIFEST.md).
|
||||
|
||||
|
||||
For the current read-only [Run #93 queue audit](P05-OIDC-03-A01.md) and no-executed-step limitations see P05-OIDC-03-A01. The underlying [P05-OIDC-03 CI implementation](P05-OIDC-03.md) remains awaiting the same run. Historical Run #91 exit-code blocker and safe cleanup are in [P05-OIDC-02.md](P05-OIDC-02.md). For the previous Run #90 blocker and cleanup see [P05-OIDC-01.md](P05-OIDC-01.md). For Gitea Run #89 final Login frozen build/unit/zero-advisory acceptance see [P05-SEC-02-A01.md](P05-SEC-02-A01.md). For Run #88 historical blocker and corrected helper see [P05-SEC-02.md](P05-SEC-02.md). For Gitea Run #87 findings see [P05-SEC-01.md](P05-SEC-01.md). For backend-only isolated runtime verification see [P05-CI-03.md](P05-CI-03.md); for initial full workflow and its limitations see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
For the **terminal Run #93 failure** and verified private port-8080 bind conflict, see [P05-OIDC-03-A02.md](P05-OIDC-03-A02.md). The former [queue audit](P05-OIDC-03-A01.md) is historical: the runner subsequently started job #206. The [P05-OIDC-03 CI implementation](P05-OIDC-03.md) remains unaccepted for real OIDC. Historical Run #91 exit-code blocker and safe cleanup are in [P05-OIDC-02.md](P05-OIDC-02.md). For the previous Run #90 blocker and cleanup see [P05-OIDC-01.md](P05-OIDC-01.md). For Gitea Run #89 final Login frozen build/unit/zero-advisory acceptance see [P05-SEC-02-A01.md](P05-SEC-02-A01.md). For Run #88 historical blocker and corrected helper see [P05-SEC-02.md](P05-SEC-02.md). For Gitea Run #87 findings see [P05-SEC-01.md](P05-SEC-01.md). For backend-only isolated runtime verification see [P05-CI-03.md](P05-CI-03.md); for initial full workflow and its limitations see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.
|
||||
@@ -117,3 +117,6 @@ In Gitea `vibtools/ZitPlane` → Actions → **ZitPlane P05-OIDC-01 Disposable R
|
||||
|
||||
|
||||
**P05-OIDC-03 acceptance:** The existing manual `p05-oidc-acceptance.yml` on a dedicated Gitea Docker runner will first classify the disposable socat startup and, if unhealthy, start a digest-verified official Python-only `127.0.0.1:8080` loopback forwarder within the same private proxy namespace. It then must prove the original official OIDC client/user + real Chromium Login V2/Account callback/session/negative contracts and owned-resource teardown. This changes no production secrets, identity settings, Login/Auth.js code or published host ports. Actual PASS/BLOCKED status is in `notes/P05-OIDC-03.md`.
|
||||
|
||||
|
||||
**P05-OIDC-03-A02 terminal result:** [Run #93](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/93) **started and FAILED**, so the previous “runner queued” blocker is no longer current. Four-service portless ZITADEL stack and private Traefik routing worked; socat and Python fallback both failed binding private TCP port 8080 (`SOCKET_BIND_ERROR` / `ADDRESS_IN_USE`). Neither official test OIDC client/user nor actual Chromium Login V2/Auth.js session was exercised; mandatory cleanup PASS. No changes to this setup or production. Inspect verified socket ownership only in a **separately approved disposable CI** before selecting a network/port remedy. See `docs/P05-OIDC-03-A02.md`.
|
||||
@@ -74,3 +74,8 @@ Job #197 in [Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) fai
|
||||
## P05-OIDC-03-A01 — Gitea Run #93 queued, job not started
|
||||
|
||||
Existing Gitea Run #93/job #206 has not been assigned a running job at the inspected snapshot: no steps, no actual start timestamp and job log API returns `404 job not started`. Workflow `p05-oidc-acceptance.yml` is active and requests `ubuntu-latest`. This **does not prove** the runner is offline, that labels mismatch, or that the Python/socat forwarder failed. To investigate, have a suitably authorized Gitea administrator inspect runner online status, matching labels and capacity **without changing settings**. Do not manually dispatch another run or open production ports. No Run #93 teardown occurred because no resources were created. Details: `notes/P05-OIDC-03-A01.md`.
|
||||
|
||||
|
||||
## P05-OIDC-03-A02 — Run #93 real terminal blocker, not a runner-queue outage
|
||||
|
||||
Previously queued Run #93 eventually ran: job #206 started and failed after healthy backend/proxy. Socat and Python fallback both could **not bind private 127.0.0.1:8080**. Socat classified `SOCKET_BIND_ERROR`; Python explicitly `ADDRESS_IN_USE`. That is strong evidence of a **port collision**, but there is **no verified socket inode/process owner yet**; do not attribute it to Traefik, ZITADEL or another process by guess. Do not disable issuer/PKCE checks, expose host 8080, reuse production secrets, or edit original backend/Account code. Safe next step requires separate approved CI-only private listener inspection before forwarding. Existing `always()` cleanup PASS; no residual run-owned containers/network/secrets. Full evidence: `docs/P05-OIDC-03-A02.md`.
|
||||
Reference in new issue
Block a user