admin/felhom-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record POSITIVE post-deploy verification for v0.176.0

Browse Source 
The quiesce loop is silent by design when nothing is due, so 'no error lines' is
not evidence. The observable that is: every /backup/due makes the agent read that
tier's storage content, which lands in pveproxy/access.log. Both tiers polled
every 5 min, both HTTP 200, tick phase consistent with the deploy restart.
This commit is contained in:
authentik Default Admin
2026-07-27 16:36:30 +02:00
parent b8598361b8
commit ccefff4f39
1 changed files with 21 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REPORT.md
+21 -2
View File
@@ -89,8 +89,27 @@ also pass against a gate that was simply disabled); and
## Deployed ## Deployed
`gitea.dooplex.hu/admin/felhom-controller:0.176.0` — **demo-hp first, then demo-felhom**, both `gitea.dooplex.hu/admin/felhom-controller:0.176.0` — **demo-hp first, then demo-felhom**, both
`Up … (healthy)`, both logging `[quiesce] loop started (poll 5m0s, max-quiesce 30m0s)` with **no** `Up … (healthy)`, both image digests matching the DooPlex build byte-for-byte
backoff or deferral lines across two full poll intervals. (`sha256:98fcbc677bfa1ab8…`), both logging `[quiesce] loop started (poll 5m0s, max-quiesce 30m0s)`.
**Positive confirmation the loop still works, not merely the absence of complaints.** The quiesce
loop is *silent by design* when nothing is due (`len(dueTiers) == 0 → return nil`), so "no error
lines" proves nothing on its own. The observable that does prove it is the agent's per-tier
due-check: every `/backup/due` makes the agent read that tier's storage content (R-84 ground truth),
which lands in `pveproxy/access.log`. On demo-felhom after the deploy:
```
16:28:44 +0200 GET …/storage/local/content 200
16:28:45 +0200 GET …/storage/felhom-pbs/content 200
16:33:44 +0200 GET …/storage/local/content 200
16:33:45 +0200 GET …/storage/felhom-pbs/content 200
```
Both tiers polled every 5 minutes, both answering **200** — so the loop is ticking, both tiers are
being evaluated, and the storage reads succeed (real ages, no nil, no valve firing). The tick phase
shifted from `:02:57/:07:58/:12:57` to `:28:44/:33:44`, which is the 14:23:43 UTC restart resetting
the ticker — consistent with the deploy and nothing else. **Zero backoff or deferral lines on either
box**, and no vzdump attempted since the incident's last failure at 07:13:06 UTC.
## NOT yet live-validated ## NOT yet live-validated