chore(deps): update dependency dra-driver-nvidia-gpu

[renovate]

This PR contains the following updates:

Package	Update	Change
dra-driver-nvidia-gpu	patch	0.4.0-1.azl3 → 0.4.1-2.azl3
dra-driver-nvidia-gpu	patch	0.4.0-ubuntu24.04u2 → 0.4.1-ubuntu24.04u2
dra-driver-nvidia-gpu	patch	0.4.0-ubuntu22.04u1 → 0.4.1-ubuntu22.04u2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

Failed gate run

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169474350
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E

Detective summary

Test_LocalDNSHostsPlugin/Ubuntu2404/scriptless_nbc reached validation, then validators.go:1010 reported localdns-exporter@...service unexpectedly entered a failed state. Timeline and build status corroborate the E2E task exit code 1; skipped image-discovery scenarios are unrelated.

Likely cause and signature

Known LocalDNS exporter unit-state failure, signature localdns-exporter-systemd-failed-state, confidence high. Strongest alternative: PR #8766 DRA driver update destabilized the node, but the PR only changes parts/common/components.json and this exact LocalDNS signature is already tracked under repair Bug #38581800.

Recommended owner/action

Node Lifecycle E2E/LocalDNS owners should continue Bug #38581800 and inspect the scenario bundle failed-unit logs; no PR author action is indicated from this evidence alone.

Evidence

• Task log: logId 538; job log: logId 545
• Wiki signature: localdns-exporter-systemd-failed-state
• Repair item: https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38581800

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[aks-node-assistant]

Failed gate run

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=170309991
Failed job/stage/task: e2e / Run AgentBaker E2E

Detective summary (three-level RCA)

TL;DR: Infrastructure infra-flake. 30 kubenet scenarios timed out at 600s node-ready wait. Not caused by this PR. Confidence: high (≥95%).

L1 – Surface failure
waiting for node X to be ready failed (600.0s) across ~30 scenarios; ##[error] Script failed with exit code: 1. All failures in kubenet default sub-tests.

L2 – Corroboration
Node condition: NetworkUnavailable=True, reason=NodeInitialization, message=Waiting for cloud routes; kubelet: cni plugin not initialized. Azure CNI scenarios all passed. Simultaneous failure with builds 170309966 (PR #8765) and 170310042 (PR #8733) in the same 3-minute window confirms shared infra event, not PR regression.

L3 – Root-cause challenge

• ❌ PR-caused regression: ruled out — three unrelated PRs fail identically and simultaneously.
• ✅ E2E infra: kubenet CCM route-table provisioning failure — CCM could not update Azure route table for pod-CIDR routes; all kubenet nodes blocked in NodeInitialization.
• Strongest alternative: transient Azure ARM throttle or CCM backoff on the shared abe2e-kubenet-v5-* cluster.

Secondary signature: wireserver-nonhost-debug-pod-missing — wireserver validation failed with failed to get non host debug pod for wireserver validation on multiple scenarios; co-effect of cluster instability.

Recommended action: Re-run; no PR change required.

Wiki: e2e-kubenet-cloud-routes-waiting-cni-uninit · wireserver-nonhost-debug-pod-missing

[aks-node-assistant]

AgentBaker Linux PR gate detective

Build: 170338424
Job: $(System.Collections.Hashtable.job)
Signature: $(System.Collections.Hashtable.sig)
Classification: Known E2E CSE/provisioning flake
Confidence: High

TL;DR: Ubuntu 22.04 HTTPSProxy PrivateDNS failed during VMSS CSE provisioning with exit 50 before kubelet start; this matches the existing repair-item signature.

Strongest alternative theory: A real proxy/CSE regression is possible, but PR scope does not point at proxy or CSE code.

Recommended next action: Track under repair item #38559852; PR author can rerun, no immediate code action indicated.

Wiki source of truth: https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[aks-node-assistant]

Clawpilot AgentBaker Linux Gate Detective

• Run: 171191672
• Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E
• TL;DR: E2E validation reached the node, then wireserver-blocking validation failed because debug-pod exec through apiserver/kubelet returned context deadline / 502 streaming errors.
• Signature: wireserver-exec-context-deadline-kubelet-streaming
• First failing step: Task log 553: Test_Ubuntu2404Gen2/default and Test_Ubuntu2404Gen2_McrChinaCloud/default failed during wireserver validation.
• Likely root cause: Shared-cluster/apiserver-to-kubelet exec streaming flake, not a VHD build failure.
• Classification: E2E test infrastructure / apiserver-kubelet exec streaming flake
• Assessment: Infra/test-code likely; product regression unlikely; PR-change-caused weak because this PR only updates DRA driver in components.json.
• Confidence: Medium-high
• Strongest alternative: A transient kubelet/network issue on the provisioned Ubuntu2404 node could also break exec, but two scenarios failed in the same validator and the VM had reached validation first.
• Recommended owner/action: AgentBaker E2E/shared-cluster network owner: inspect kubelet streaming and wireserver validator retries; PR owner likely no action unless this repeats only on the PR.
• Evidence: timeline marks the E2E stage/job/task failed with exit code 1; task log 553 contains the first failing scenario and primary error; PR metadata shows changed files: parts/common/components.json.