recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

STATUS: lasuite upgrade is a convergence failure (not rate-limit) post quota-reset; diagnosing
continuous-integration/drone/push Build is passing
Details

Browse Source 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-05-27 11:29:01 +01:00
co-authored by Claude Opus 4.7
parent 78250bc8ce
commit 0632301240
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
STATUS.md
+10 -2
View File
@@ -67,8 +67,16 @@ Drone build with RECIPE=<r> (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 - **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. the recipe-CI pipeline will set `CCCI_JANITOR_MAX_AGE=0` (safe — no concurrent runs). See DECISIONS.
## Blocked ## Blocked / investigating — lasuite-docs upgrade stage (the only D10 gap)
- **Docker Hub anonymous pull rate limit — registry pull creds needed (A1, operator).** During the - **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 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 `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 → Rejected "No such image" → couldn't pull). Confirmed: `docker pull redis:8.2.6` on the node →