Files
felhom.eu/documentation/tests/golden-0.232.0-2026-09-01/12-selfupdate.txt
T
admin 63eff21a5c
gates / gates (push) Successful in 17s
golden 0.232.0 baked, vouched, floor raised — and it carries TWO releases
GOLDEN_SHA256 5f8a53ed5b19a6cb2006298ce6239f6fca2b990cc3ef6eada89f602801ca91b8,
657 494 489 B. 0.231.0 was never baked, so the fleet went 0.230.0 -> 0.232.0.

THE CHECK THE 0.230.0 BAKE SKIPPED, AND THIS ONE DID NOT: the bake script's fingerprint was
compared ACROSS THE HOP - 7b0fb5cf...73b6a1 on DooPlex and inside the VM. The previous bake
recorded only the DooPlex-side hash and said so; this one is a measurement.

Three independent readers agreed before anything was vouched: the bake's own print, the round
trip of the published bytes (HTTP 200, 657494489 B, same sha, hashed from what was
downloaded), and the hub's Day-0 dropdown reading Gitea on a different code path. The
delivered artifact names its own controller - ./etc/felhom-controller-image reads
felhom-controller:0.232.0 - with 19382 entries under var/lib/felhom/docker/.

Both pre-gates were shown able to see something before their zeroes were believed, and the
manifest was RE-READ after vouching rather than trusted from the 303 flash.

DELIVERY WAS ACTUALLY EXERCISED. Both boxes had been hand-deployed during validation, so the
floor had nothing to move. Rather than report delivery untested, demo-felhom was rolled back
to 0.231.0 and the chain run for real - it moved itself in ~20s:
  10:47:16 controller-swap: image file written, restarting bootstrap  target=...0.232.0
  10:47:26 controller-swap: new controller healthy                    target=...0.232.0

And this is the first bake golden_currency_gate.py actually gates: it now reads the
GOLDEN_SHA256 line out of the bake log rather than matching a directory name (R-410, shipped
hours earlier the same day). All 13 felhom.eu gates are green, golden-currency included, for
the first time since v0.230.0 was released.
2026-09-01 10:50:54 +02:00

21 lines
1.5 KiB
Plaintext

=== both boxes were HAND-DEPLOYED during validation, so the floor had nothing to move.
Rolling demo-felhom back to 0.231.0 so the delivery chain is actually exercised. ===
rolled-back-to-0.231.0
now: gitea.dooplex.hu/admin/felhom-controller:0.232.0
=== waiting for the agent to pull it up to the floor ===
MOVED ITSELF after ~20s
final: gitea.dooplex.hu/admin/felhom-controller:0.232.0
=== demo-felhom's OWN agent journal — the self-update, in its words ===
Sep 01 10:47:16 demo-felhom felhom-agent[2564828]: time=2026-09-01T10:47:16.761+02:00 level=INFO msg="controller-swap: image file written, restarting bootstrap" vmid=9201 target=gitea.dooplex.hu/admin/felhom-controller:0.232.0
Sep 01 10:47:26 demo-felhom felhom-agent[2564828]: time=2026-09-01T10:47:26.188+02:00 level=INFO msg="controller-swap: new controller healthy" vmid=9201 target=gitea.dooplex.hu/admin/felhom-controller:0.232.0
=== both boxes, final ===
hp: gitea.dooplex.hu/admin/felhom-controller:0.232.0 Up 17 minutes (healthy)
felhom-pve: gitea.dooplex.hu/admin/felhom-controller:0.232.0 Up 23 seconds (healthy)
=== the golden gate — the first bake it actually gates (R-410) ===
newest released controller : 0.232.0 (## v0.232.0 — one writer at a time, and a check that can actually run (2026-09-01, R-411/R)
newest golden baked : 0.232.0 (documentation/tests/golden-0.232.0-2026-09-01 [sha 5f8a53ed5b19…])
golden currency gate OK — the newest released controller has a golden (NOTE: this checks the BAKE, not the vouch — see the module docstring)