fix(ai): keep openclaw before gemini in alert fallback
All checks were successful
Code Review / ai-code-review (push) Successful in 10s
CD Pipeline / tests (push) Successful in 1m9s
CD Pipeline / build-and-deploy (push) Successful in 3m28s
CD Pipeline / post-deploy-checks (push) Successful in 1m19s

This commit is contained in:
Your Name
2026-05-06 20:20:44 +08:00
parent bcb9397c38
commit d0e98192de
3 changed files with 33 additions and 0 deletions

View File

@@ -4129,3 +4129,8 @@ DATABASE_URL='postgresql+asyncpg://test:test@localhost:5432/test' \
- 這次不是要禁 Gemini而是恢復正確順序GCP-A/GCP-B/111 優先OpenClaw/Nemo 作為 cloud 仲裁備援Gemini 只保留最後備援。
- `openclaw_nemo` 在修補前仍被 Redis control disabled需等 AWOOOI 新 image 部署後,再依現場測試結果解除 disabled避免舊 image 仍直接跳 Gemini。
### 20:18 追加
- 第一版部署後 live 檢查發現 Ollama failover chain 的 cloud candidates 仍可能只有 `gemini`;已再補強 resolver只要 AI control 未停用 `openclaw_nemo`,告警路徑會主動把它插入 Gemini 前面;若 Redis control 顯示 disabled則會明確移除不繞過人工控制。
- 新增測試覆蓋 disabled 狀態:`openclaw_nemo` disabled 時 provider order 仍維持 `ollama_gcp_a → ollama_gcp_b → ollama_local → gemini`