journal(2): consumed orchestrator inbox + re-baseline (new Hetzner box 8GB/135GB free); launched discourse full6

This commit is contained in:
autonomic-bot
2026-05-31 04:34:54 +00:00
parent c01225b841
commit 3dc8fdf507

View File

@ -1540,3 +1540,21 @@ no SSO for STAGES=install,upgrade,backup,restore,custom. Result: available RAM 6
stacks total ~70 MiB (traefik 33 / drone 7 / dashboard 13 / bridge 14 / backups 2). discourse now gets
nearly the whole node vs competing with keycloak's ~700MB java during asset-precompile. Pre-pulling
`bitnamilegacy/discourse:3.3.1` by TAG (full5 fix #1: inline deploy pull → no-op). Launch on image-ready.
---
## 2026-05-31T04:3xZ — RESUMED loop; consumed orchestrator inbox; launched discourse full6 (Builder)
Re-oriented from STATUS-2/REVIEW-2/JOURNAL-2. Consumed `machine-docs/BUILDER-INBOX.md` (orchestrator
heads-up, commit `c01225b`). **Re-baseline per the heads-up — my prior OOM/disk-starved/rate-limit notes
were about the OLD Incus box and are STALE:** the live `ssh cc-ci` is the new Hetzner box `cc-ci-hetzner`
(tailnet 100.95.31.88, public 91.98.47.73), NVMe, **~8 GB RAM**, **150 GB disk / ~135 GB free**,
**authenticated Docker Hub pulls** (no anon rate-limit). `df`/`free` re-checked: load ~0.08, 6 GiB avail,
6% disk. DNS for `*.ci.commoninternet.net` is mid-cutover to 91.98.47.73 (TTL ≤3h) — treat public-URL
flakes during the window as DNS, not a defect.
Node verified clean (no discourse/ghost stacks/volumes/secrets); warm-keycloak already shed; image
`bitnamilegacy/discourse:3.3.1` pre-cached by TAG. builder-clone fast-forwarded to origin/main.
**Launched discourse full6** (re-run of the OOM-lost full5, identical committed shape): `RECIPE=discourse
PR=1 REF=3758522cf8702e97e88cd38d47165cf14defe74e SRC=recipe-maintainers/discourse cc-ci-run
runner/run_recipe_ci.py` → `/root/ccci-discourse-full6.log`, PID 50718. Stages: install,upgrade,backup,
restore,custom (full upgrade-to-latest, required by the DONE VETO). prepull rc=15 (dangling
`sidekiq.depends_on:[discourse]`) is the known-harmless lint failure — image pre-cached, inline pull a
no-op. Polling ~5min per §7 case 1.