Repository navigation
fix fixAzureLinuxV3Gen2Kata - #9690
Sri Harsha (SriHarsha001) wants to merge 3 commits into
Conversation
AgentBaker Linux gate detectiveRun: 183921579 Detective summary: The E2E run completed 192 scenarios with 26 passed, 0 flaky, 74 skipped, and 92 failed. The failures are broad VMSS creation failures where ARM reports quota / not enough regional vCPU quota in WestUS3 before nodes can be provisioned. Likely cause/signature: �2e-westus3-vmss-quota-exceeded — shared WestUS3 regional vCPU quota/capacity exhaustion during E2E VMSS creation. Confidence: High. Timeline isolates the failure to Run AgentBaker E2E; the task log shows many scenarios failing before validation at VMSS create with quota guidance; this repeats the same signature seen in PR #9484 runs; PR #9690 changes Kata/containerd/CSE code, but the failing scenarios do not reach node provisioning. Recommended owner/action: Gate/infra owners should restore or raise WestUS3 quota/capacity for the E2E subscription/region before rerunning. No PR code action is indicated by this run. Strongest alternative: PR #9690 directly touches Kata/containerd templates and validators, so PR-caused E2E failures are possible in principle; however the observed failures happen at ARM VMSS creation due to quota, before the PR code path can be validated. Evidence: run, E2E task log, wiki signature |
PR Title Lint Failed ❌Current Title: Your PR title doesn't follow the expected format. Please update your PR title to follow one of these patterns: Conventional Commits Format:
Guidelines:
Examples:
Please update your PR title and the lint check will run again automatically. |
Windows Unit Test Results 3 files 18 suites 1m 12s ⏱️ Results for commit 31df3c1. ♻️ This comment has been updated with latest results. |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
AgentBaker Linux gate detectiveRun: 183955650 Detective summary: Build VHD completed for AzureLinuxV3 Kata, but Test/Scan failed Likely cause / signature: Confidence: Medium-high for VHD content/package regression surfaced by Test/Scan. Recommended owner/action: PR owner should verify package expectations for AzureLinuxV3 Kata and either restore/install the expected containerd package or update the content test for the intended runtime package. Strongest alternative: A transient test VM package-query issue is possible, but the task reached the validation VM and repeated the same deterministic content-test error. Evidence: build run, failed timeline records, focused failed task log, build metadata, PR changed files, and wiki tracker. |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #