From 06323012400005fc34aaf42ae709c36d75232710 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Wed, 27 May 2026 11:29:01 +0100 Subject: [PATCH] STATUS: lasuite upgrade is a convergence failure (not rate-limit) post quota-reset; diagnosing Co-Authored-By: Claude Opus 4.7 (1M context) --- STATUS.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/STATUS.md b/STATUS.md index 6ebe2d0..b794453 100644 --- a/STATUS.md +++ b/STATUS.md @@ -67,8 +67,16 @@ Drone build with RECIPE= (or `cc-ci-run runner/run_recipe_ci.py` with RECIPE/ - **Janitor backstop** for SIGKILL'd builds (reaps orphaned run apps at run-start). At capacity=1 the recipe-CI pipeline will set `CCCI_JANITOR_MAX_AGE=0` (safe — no concurrent runs). See DECISIONS. -## Blocked -- **Docker Hub anonymous pull rate limit — registry pull creds needed (A1, operator).** During the +## Blocked / investigating — lasuite-docs upgrade stage (the only D10 gap) +- **UPDATE 2026-05-27 (post quota-reset):** the Docker Hub limit reset; lasuite **install pulled + + passed** on a fresh quota (build #105), and **backup passed** — but the **upgrade stage still fails + `FATA deploy failed`**, now a genuine **convergence failure** (a service unhealthy during the + 0.3.2→0.3.3 rolling upgrade), NOT rate-limit/disk/RAM (stop-first updates; 4.6G free RAM; images + cached). It PASSES on the catalogue/canonical path (Drone #57, all 3 stages) but fails on the + mirror-clone real-`!testme` path — root cause undetermined. Running an instrumented diagnostic + (`/tmp/diag_lasuite.py`) to capture which service fails + its logs. Registry creds (below) remain + recommended for reproducibility but are NOT the fix for this convergence failure. +- **Docker Hub anonymous pull rate limit — registry pull creds (A1, operator) — recommended.** During the D10 real-`!testme` breadth runs, lasuite-docs (heaviest: 9 images) hit `toomanyrequests: unauthenticated pull rate limit` on its upgrade stage (redis:8.2.6 task Rejected "No such image" → couldn't pull). Confirmed: `docker pull redis:8.2.6` on the node →