Files
felhom.eu/documentation/audits/update-arc-2026-09-21/14-update-complete.txt
T
admin 0c263c77f2
gates / gates (push) Successful in 24s
Update arc resumed: the state measured, R-524/R-520/R-589/R-469 closed, seven questions put to the operator
Phase 0 — measured, never estimated:
- both demo boxes: 10 apps, 0 behind, 0 unknown
- 46 of 58 exact catalog pins are behind upstream; 39 within a major, 7 across
- 6 of 7 measurable floating pins have been repushed since the catalog set them
  (R-446 is no longer theoretical)
- the "23 of 66 floating pins" figure repeated in four places was STALE; recounted
  to 10, with the definition written down beside it

Three claims in the brief corrected, named first:
- R-589 was NOT open — it shipped in v0.258.0; only the row was stale
- the chaos-night canary is NOT a defect — both gates refused to certify by design
- the hub half of the report confirmed, with the nuance that the raw payload is
  stored whole, so Slice 7 is cheaper than the row implies

Closed: R-524 (controller v0.260.0, proven live in both languages), R-520 (power cut
during a REAL version change — the pin goes back, the app runs, the page says so),
R-589, R-469 (MariaDB half). Filed: R-605, R-606. R-462's stale scope corrected.

09 gains §3 decision 10 (decided by CC unattended — operator may reverse), §3b with
the seven questions in the decision shape, §6.2/6.3 the two open slices, and §6.4 an
update night costed from R-462's real numbers.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-21 13:13:23 +02:00

65 lines
4.7 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
### STEP 6 — POST the update again, let it run to completion
-- POST /api/stacks/uptime-kuma/update --
{"ok":true,"data":{"accepted":true,"completed":false},"message":"Frissítés elindult – az állapot a kártyán követhető"}
HTTPCODE:202
-- phase timeline observed (poller) --
11:08:47Z "update_phase":"pulling"
11:08:58Z "update_phase":"verifying"
11:09:09Z "update_phase":"done"
[exited with code 0]
-- state after the update completed --
update_phase : done | Frissítve
update_error : None
updating : False
state : running
containers : [('louislam/uptime-kuma:2.5.0', 'Up 25 seconds (healthy)')]
installed_images: {'uptime-kuma': ('louislam/uptime-kuma:2.5.0', 'sha256:a8610b3b4c38077922b...')}
pinned_images : {'uptime-kuma': 'louislam/uptime-kuma:2.5.0'}
catalog_images : {'uptime-kuma': 'louislam/uptime-kuma:2.5.0'}
health_probe : {'healthy': True, 'last_check': '2026-09-21T11:09:07.392077664Z', 'details': [{'type': 'http', 'target': ':3001/', 'healthy': True, 'status': 302, 'latency': '3ms'}]}
-- app.yaml on disk --
installed_images:
uptime-kuma:
ref: louislam/uptime-kuma:2.5.0
digest: sha256:a8610b3b4c38077922ba51b036691e06887d7cefd91fe620fd3d6d23d03dc240
at: "2026-09-21T11:09:07Z"
pinned_images:
uptime-kuma: louislam/uptime-kuma:2.5.0
-- live compose image line --
image: louislam/uptime-kuma:2.5.0
-- controller log, the completed update --
2026/09/21 11:06:12 update.go:904: [WARN] [stacks] update recovery: uptime-kuma was interrupted in pulling (started 2026-09-21T11:04:52Z) — nothing had run; putting the pin back
2026/09/21 11:06:12 pin.go:93: [INFO] [stacks] pin uptime-kuma: uptime-kuma=louislam/uptime-kuma:2.4.0
2026/09/21 11:06:12 update.go:705: [INFO] [stacks] update uptime-kuma: pin and definition PUT BACK to the pre-update version (uptime-kuma=louislam/uptime-kuma:2.4.0)
2026/09/21 11:06:12 dbdump.go:169: [DEBUG] DiscoverDatabases: skipping container uptime-kuma (image=louislam/uptime-kuma:2.4.0, not a database)
2026/09/21 11:06:32 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 10s ago, effective interval 5m0s, healthy=true
2026/09/21 11:06:42 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 20s ago, effective interval 5m0s, healthy=true
2026/09/21 11:06:52 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 30s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:02 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 40s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:12 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 50s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:22 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m0s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:32 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m10s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:42 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m20s ago, effective interval 5m0s, healthy=true
2026/09/21 11:07:52 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m30s ago, effective interval 5m0s, healthy=true
2026/09/21 11:08:02 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m40s ago, effective interval 5m0s, healthy=true
2026/09/21 11:08:12 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 1m50s ago, effective interval 5m0s, healthy=true
2026/09/21 11:08:22 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 2m0s ago, effective interval 5m0s, healthy=true
2026/09/21 11:08:32 healthprobe.go:53: [DEBUG] [stacks] RunHealthProbes: skipping uptime-kuma — last check 2m10s ago, effective interval 5m0s, healthy=true
2026/09/21 11:08:42 auth.go:142: [DEBUG] [web] auth: valid session for POST /api/stacks/uptime-kuma/update
2026/09/21 11:08:42 router.go:81: [DEBUG] [api] POST /api/stacks/uptime-kuma/update (path=/stacks/uptime-kuma/update)
2026/09/21 11:08:42 router.go:582: [INFO] [api] update requested for stack: uptime-kuma
-- badge now that installed == catalog (2.5.0) --
<span class="tag tag-ok" title="Ez az alkalmazás a legfrissebb elérhető változatot futtatja.">Naprakész</span>
<span class="tag tag-ok" title="This app is running the newest version available.">Up to date</span>
-- container now serving --
uptime-kuma | louislam/uptime-kuma:2.5.0 | Up 40 seconds (healthy)