[Incident] [incident] aoai-model deployment failure: Smoke Azure Codex and Smoke Azure PI engine steps exit 1
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 43/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- azure, github-actions, go
- 领域
- ci-cd, infrastructure
调研方向
Start with the linked failed runs and inspect the Execute Codex CLI and Execute Pi CLI step logs for the driver stderr and exit reason. Then check the aoai-model environment variables, federated credential subject, Entra-authenticated AWF proxy, and Azure OpenAI deployment. Done means both smoke workflows pass when rerun with workflow_dispatch.
由索引模型根据 Issue 内容生成。
描述
Summary
Deployments to the aoai-model environment are failing on main at commit c4fffbf1eb. The failing deployments come from two scheduled smoke workflows, Smoke Azure Codex and Smoke Azure PI. In both, the engine step exits with code 1 about 30 seconds after it starts. The same failure has recurred on every scheduled run since 2026-11-03.
Failing runs and deployments
| Workflow | Run | Failing engine step | Agent job |
|---|---|---|---|
| Smoke Azure Codex | 43334288414 | Execute Codex CLI | 131586831744 |
| Smoke Azure PI | 43334109551 | Execute Pi CLI | 131586277653 |
Failed aoai-model deployments: 7753171242, 7753186837, 7753201642 (all failure, 00:08 to 00:09 UTC on 2026-11-13).
Likely root cause
- Both engine steps fail the same way. The driver exits with code 1 before a terminal safe output is recorded, and the
conclusionjob then runsHandle agent failure. - Shared setup steps (MCP gateway, safe-outputs config, AWF install, container download) all pass. The failure is limited to the engine step. That points at Azure OpenAI inference through the Entra-authenticated AWF proxy (
provider: azure, OIDC viaAZURE_TENANT_ID,AZURE_CLIENT_ID,AI_GATEWAY_SCOPE). - Earlier auto-filed incidents for these workflows (for example #74268 and #76646) were classified
driver_crash, which matches. - The failures began 2026-11-03 across six different commit SHAs, so no single recent commit explains them. The firewall bump
838595e127postdates that first failure and is not the trigger. - This is an inference. The engine stderr could not be read (see below).
Evidence limitation
gh run view --log-failed returns HTTP 403 (DIFC policy violation) for these runs, so the engine output was not available. The findings above come from job step metadata, check-run annotations, and prior incident records.
Job step timings and annotations
- Codex agent job 131586831744: Execute Codex CLI 00:07:38 to 00:08:08 UTC, failure. Annotation:
Agent execution exited with code 1. - Pi agent job 131586277653: Execute Pi CLI 00:06:39 to 00:07:08 UTC, failure. Annotation:
Agent execution exited with code 1. - Conclusion jobs 131587683233 and 131587268644:
Handle agent failurefailed. - Sibling
smoke-copilot-aoai-entrais intermittent: success on 2026-11-09, failure on 2026-11-11 (run 42929934126).
Suggested remediation
- Open the failed Execute Codex CLI and Execute Pi CLI steps in the run links above. Capture the driver stderr and exit reason.
- Confirm the
aoai-modelenvironment variablesAZURE_TENANT_ID,AZURE_CLIENT_ID, andAI_GATEWAY_SCOPEare set. Confirm the federated credential subject matches the environment. - Check token acquisition and health of the Entra-authenticated AWF proxy and the Azure OpenAI deployment used by these smokes.
- After a fix, re-run both smoke workflows with
workflow_dispatchand confirm they pass before closing this incident.
Generated by 🚨 Deployment Incident Monitor · copilot · routed: haiku55 xhigh · ~3 AIC · ⌖ ~1 AIC · ⊞ 2.9K · ◷
- expires on Nov 19, 2026, 4:15 PM UTC-08:00
- 主要语言
- Go
- 星标
- 5.6k
- 派生
- 625
- 平均合并
- 5 小时 39 分钟
- 30 天内合并 PR
- 796
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/gh-aw 的其他 Issue
-
agent-research cookie
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
automation observability optimization traces
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
Protected session capture: `Parse agent logs for step summary` fails when the engine step never ran未关闭ai-inspected
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
awf community
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
automation cli-tools testing
难度 1/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
相似的 Issue
-
type:bug
难度 2/5 1-3 小时 新手友好度 72/100
nightgauge/nightgauge#3266 ·
维护者通常 1 天内回复
-
area: ai-models priority: normal
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
prime-radiant-inc/evener#6325 ·
维护者通常 1 天内回复
-
team:library-maintainers
难度 2/5 1-3 小时 新手友好度 82/100
padok-team/burrito#1208 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
bazel-contrib/rules_go#4784 · 1 条评论 ·
维护者通常 1 天内回复