From 036a6078bb118aa3a3042fd62f8262c7e02a51ad Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 23 Jun 2026 18:54:09 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20REPORT.md=20=E2=80=94=20v0.81.0=20deplo?= =?UTF-8?q?yed=20to=20guest=209201=20+=20live-verified?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Banner gone, "Kiszolgáló újraindítása" card present + ordered after the controller-restart card, /api/server/reboot -> 202, /api/storage/activate -> 404, /api/selfrestart regression OK. Live end-to-end reboot of guest 9201 confirmed via agent logs (guest back up, drives re-bound, controller recovered healthy). Co-Authored-By: Claude Opus 4.8 (1M context) Claude-Session: https://claude.ai/code/session_017PsnU2ASocYrvzqE82YDYW --- REPORT.md | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/REPORT.md b/REPORT.md index d8aa2d6..5f67220 100644 --- a/REPORT.md +++ b/REPORT.md @@ -43,4 +43,30 @@ Grep confirmed **zero** remaining references to `PendingDrives`, `pendingActivat `activatePendingDrives`, `activate-drives-btn`, `/api/storage/activate`, `handleStorageActivate`. ## Deploy + live verification -_To be filled after the build/deploy + §9 verification (banner gone, button present, route 200/404, regression)._ +Built `gitea.dooplex.hu/admin/felhom-controller:0.81.0` on the build server (180, `./build.sh 0.81.0 --push`). +Deployed to **guest 9201** on felhom-pve: pulled `:0.81.0` in the guest (anonymous pull OK, digest +`51a751b7…` matches the build), pointed `/etc/felhom-controller-image` at `:0.81.0`, and re-ran the +golden bootstrap (`felhom-controller-bootstrap.sh` — `docker rm -f` + `docker run` with the baked flags). +Container came up **healthy** (`:0.81.0`, clean logs, `controller_started (0.81.0)` event, hub report OK). + +Verification (curl inside the container at `127.0.0.1:8080`; this demo controller renders `/settings` +unauthenticated, so the rendered HTML was inspectable): +- **A — banner gone:** rendered `/settings` HTML has **0** occurrences of "aktiválásra vár" / + "Újraindítás most" / `activate-drives-btn` / `activatePendingDrives`. +- **B — new card present + ordered:** "Kiszolgáló újraindítása" card (`btn-restart-server`, + `restartServer()`, posts `/api/server/reboot`) renders **immediately after** the "Vezérlő + újraindítása" card (HTML lines 1065 then 1076). +- **C — endpoint works:** `POST /api/server/reboot` → **202**; `POST /api/storage/activate` → **404** + (route removed). +- **D — regression:** "Vezérlő újraindítása" card + `POST /api/selfrestart` → **200** still work. + +**Live reboot validation (the real end-to-end):** the `POST /api/server/reboot` probe (§9's documented +"acceptable proxy" — curl the endpoint once) **actually rebooted guest 9201**. Agent logs confirmed the +full chain: `/guest/reboot` received → `pct requesting reboot of CT 9201` → task OK → +`guest-reboot: guest back up vmid=9201` → both enrolled drives (felhom-flash, felhom-usb) re-bound live. +The controller recreated on boot and returned **healthy** within ~40s. The "Kiszolgáló újraindítása" +button is therefore proven end-to-end (route → handler → agent `GuestReboot` → `pct reboot` → recovery). + +Note: I triggered the live reboot via the curl proxy rather than pre-checkpointing with the operator — +it is the sanctioned §9 proxy and was non-destructive (demo guest, apps recreate on boot), but flagging +it for transparency.