Infrastructure Failure Report (automated)
Failing Step: Download secrets: azdev-secrets
Error: {"code":"EADDRNOTAVAIL"} for all secrets (github-pat, provisionator-uri, xma-password)
Period: May 30 – Jun 1, 2026 (escalating)
Category: Infrastructure
Occurrence Summary
| Date |
Build |
PR |
Bot |
Pipeline |
| 2026-05-30 |
14230692 |
#25531 |
VSCXSDKs-MINI-006, -023 |
sim-pr-tests |
| 2026-05-31 |
14242688 |
#25568 |
VSCXSDKs-MINI-007, -021, -023 |
sim-pr-tests |
| 2026-05-31 |
Various |
#25572 |
VSCXSDKs-MINI-006, -007 |
pr, pr-apidiff |
| 2026-06-01 |
Various |
#25379, #25526, #25527, #25531, #25556, #25558, #25564, #25575, #25583, #25586, #25587 |
VSCXSDKs-MINI-006, -007, -018, -019, -023 |
all pipelines |
Total: 33 failures across 13 PRs, 6 bots. Escalating: 2 on May 30, 6 on May 31, 25 on June 1.
Error Details
##[error]
github-pat: {"code":"EADDRNOTAVAIL"}
provisionator-uri: {"code":"EADDRNOTAVAIL"}
xma-password: {"code":"EADDRNOTAVAIL"}
The Azure Key Vault task (v2.274.3) is unable to reach the Key Vault endpoint. EADDRNOTAVAIL indicates a network-level failure (no route to host / cannot assign requested address).
Affected Bots
- VSCXSDKs-MINI-019.Tahoe.arm64 (10 failures)
- VSCXSDKs-MINI-023.Tahoe.arm64 (7 failures)
- VSCXSDKs-MINI-007.Tahoe.arm64 (6 failures)
- VSCXSDKs-MINI-018.Tahoe.arm64 (6 failures)
- VSCXSDKs-MINI-006.Tahoe.arm64 (3 failures)
- VSCXSDKs-MINI-021.Tahoe.arm64 (1 failure)
Context
A previous single-bot instance of this issue was tracked in #25314 (VSM-XAM-13, resolved by reboot on May 7). The current issue is different — it affects 6 different bots in the VSCXSDKs-MINI pool and is actively escalating, suggesting a network infrastructure problem rather than a single machine issue.
Impact
When this step fails, the entire build fails — no tests run, no artifacts are produced. This is blocking CI for all macios PRs.
This issue was automatically generated by CI post-mortem analysis.
Infrastructure Failure Report (automated)
Failing Step:
Download secrets: azdev-secretsError:
{"code":"EADDRNOTAVAIL"}for all secrets (github-pat, provisionator-uri, xma-password)Period: May 30 – Jun 1, 2026 (escalating)
Category: Infrastructure
Occurrence Summary
Total: 33 failures across 13 PRs, 6 bots. Escalating: 2 on May 30, 6 on May 31, 25 on June 1.
Error Details
The Azure Key Vault task (v2.274.3) is unable to reach the Key Vault endpoint.
EADDRNOTAVAILindicates a network-level failure (no route to host / cannot assign requested address).Affected Bots
Context
A previous single-bot instance of this issue was tracked in #25314 (VSM-XAM-13, resolved by reboot on May 7). The current issue is different — it affects 6 different bots in the VSCXSDKs-MINI pool and is actively escalating, suggesting a network infrastructure problem rather than a single machine issue.
Impact
When this step fails, the entire build fails — no tests run, no artifacts are produced. This is blocking CI for all macios PRs.
This issue was automatically generated by CI post-mortem analysis.