docs(awooop): record t135 runner ownership evidence [skip ci]

This commit is contained in:
Your Name
2026-05-21 19:10:21 +08:00
parent 5aa46bc95e
commit da8456cf07
2 changed files with 112 additions and 0 deletions

View File

@@ -2657,6 +2657,14 @@ Phase 6 完成後
- 判讀T134 收斂 runner workspace cleanup false noise讓 CI/CD log 更接近真訊號;不等於 runner ownership 完全治理。下一段應處理 110 host-level act_runner 與 Docker-wrapped `gitea-runner` 雙 daemon 衝突、stale `b5-test-net`、API image `apt-get` / `chown -R appuser` 與 Web `next build` 的 20 分鐘 build pressure、Playwright apt duplicate source warnings。
- 目前進度更新AwoooP 告警可觀測鏈約 99.998%Incident-level source correlation 可見性約 98.8%Source correlation apply 狀態鏈可驗證性約 99.72%Source correlation freshness / rolling gate 約 98.2%;前端 AI 自動化管理介面同步約 99.999%Dashboard snapshot / SSE console noise 收斂約 99.2%CI/CD runner hygiene 約 98.8%Build host pressure治理約 76%;完整 AI 自動化管理產品化約 99.959%。
**T135 Gitea runner ownership drain 與 stale network cleanup2026-05-21 台北)**
- 觸發T134 後 live 110 仍同時跑 host-level `gitea-act-runner-host.service` 與 Docker-wrapped `gitea-runner`Docker runner restart policy 是 `unless-stopped`,且最近 2 小時實際接過 `awoooi` / `stockplatform-v2` / `ewoooc` tasks與「只保留 host runner」的 runner ownership 目標衝突。
- Live 收斂:未直接硬停 active job先確認 AWOOI 無 active run再對 Docker runner 執行 `docker update --restart=no gitea-runner``docker kill --signal=SIGINT gitea-runner`。Live log 顯示 `shutdown initiated, waiting 1h0m0s...`readback 為 `Restart=no Status=exited Running=false`。空 `b5-test-net` 已移除live docker-health-monitor 仍排除 `gitea-runner`
- Repo 修正:`ops/runner/install-gitea-host-runner-service.sh``scripts/reboot-recovery/awoooi-startup-110.sh` 改為 active task 時送 SIGINT drain不用預設 10 秒 `docker stop``scripts/ci/cleanup-host-runner-workspace.sh` 會移除空 `b5-test-net``ops/runner/README.md` 補第五層 legacy Docker runner drain。
- Verification`bash -n``git diff --check` pass。`9b465ee1 ci(runner): drain legacy docker act runner safely` 已推 Gitea mainCode Review #2815 success手動 CD #2816 successtests job 3634 `2190 passed, 23 skipped` + B5 `5 passed` + cleanup cleanbuild-and-deploy job 3635 success約 5m15spost-deploy job 3636 Alert Chain `8/8` + E2E `5 passed` + AWOOI API success notification mirrored + cleanup clean。Deploy marker `5aa46bc9 chore(cd): deploy 9b465ee [skip ci]`production health healthy/prod/mock_mode=falseAPI/Web image `9b465ee140a32ac73742d59f589164cbce798d04` 2/2Worker 1/1 ready。110 runner readbackDocker `gitea-runner` exited/restart=no`b5-test-net` absentload 約 3.72/3.80/10.09。
- 判讀T135 已把 runner ownership 從雙 runner 搶工收斂到 host runner 單一主控;下一段不要重新啟用 Docker-wrapped runner而是做 runner pool / repo label 隔離、API image `apt-get` / `chown -R` 分層、Web build cache/offload、Playwright apt source-list hygiene。
- 目前進度更新AwoooP 告警可觀測鏈約 99.998%Incident-level source correlation 可見性約 98.8%Source correlation apply 狀態鏈可驗證性約 99.72%Source correlation freshness / rolling gate 約 98.2%;前端 AI 自動化管理介面同步約 99.999%Dashboard snapshot / SSE console noise 收斂約 99.2%CI/CD runner hygiene 約 99.2%Runner ownership 收斂約 96%Build host pressure治理約 82%;完整 AI 自動化管理產品化約 99.960%。
---
### 2026-04-20 晚 (台北) — C1-C4 全流程串接 — Playbook 鏈路保護commit de2d34d