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

[renovate]

This PR contains the following updates:

Package	Update	Change
dra-driver-nvidia-gpu	major	0.4.0-ubuntu24.04u2 → 25.12.0-ubuntu24.04u2
dra-driver-nvidia-gpu	major	0.4.0-ubuntu22.04u1 → 25.12.0-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]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168527801
Failed job/stage/task: $(System.Collections.Hashtable.job)
First failing step/test: $(System.Collections.Hashtable.first)

RCA: Known Ubuntu 22.04 HTTPSProxy PrivateDNS provisioning flake: vmssCSE returns VMExtensionProvisioningError with CSE ExitCode 50 and KubeletStartTime=n/a before kubelet starts. The failing scenario is unrelated to the GPU DRA driver update.

Confidence: High for the primary signature. Corroborated by timeline/status, focused failed logs, associated changes, and the flakiness wiki before publishing.

Strongest alternative: GPU DRA driver update caused provisioning failure; less likely because the failing scenarios are non-GPU Ubuntu 22.04 HTTPSProxy PrivateDNS and match prior watcher signature.

Recommended owner/action: E2E scenario/proxy/private-DNS owner: inspect CSE output/proxy/private DNS readiness and rerun after infra clears.

Wiki signature: $(System.Collections.Hashtable.sig) (source of truth)

[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]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=169119692
Failed job/stage/task: e2e / Run AgentBaker E2E
Summary: E2E hit the known NetworkIsolated shared-cluster cleanup failure. abe2e-azure-networkisolated-v3-d6cc9 had a deleting/missing node resource group; cleanup failed with ResourceGroupDeletionBlocked / InUseNetworkSecurityGroupCannotBeDeleted because abe2e-networkisolated-securityGroup is still attached to the shared VNET subnet.

Likely cause/signature: stale NetworkIsolated shared cluster NSG in-use (networkisolated-shared-cluster-delete-blocked-inuse-nsg, repair #38506740). Confidence: High.
Alternative considered: PR #8733's GPU DRA component bump; less likely because failure is AKS shared-cluster deletion/NSG cleanup, not GPU provisioning.
Recommended owner/action: No PR action; E2E infra owner should resolve the stuck NSG/subnet association and harden cleanup/retry.
Wiki: 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 (networkisolated-shared-cluster-delete-blocked-inuse-nsg)

[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.

[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=169474438
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E; plus build / build2204gen2containerd / Test, Scan, and Cleanup

Detective summary

E2E first failed before provisioning in Test_DCGM_Exporter_Compatibility/AzureLinux3/default: shared cluster prep hit a debugnonhost-mariner-tolerated daemonset object-modified conflict, followed by VMSS page context cancellation. Timeline and build status corroborate the E2E task failure. The VHD scan also reported known CIS rule 6.1.3.1|pass->fail in build2204gen2containerd; the scan script exited 0 but emitted a CIS regression issue.

Likely cause and signature

E2E: known test-infra race, signature debugnonhost-daemonset-write-conflict, confidence high. Strongest alternative is transient API pressure, but it matches the existing row and PR only bumps DRA driver. CIS: known Ubuntu 22.04 Gen2 containerd logfile-access signal, signature linux-vhd-prgate-cis-ubuntu2204-gen2-containerd-6131-logfiles, confidence high.

Recommended owner/action

E2E/test-infra owners should investigate the shared debug daemonset update path. Linux VHD/CIS owners should continue the existing CIS repair investigation; no PR-specific action is indicated from this evidence alone.

Evidence

• E2E task log: logId 538; job log: logId 545
• CIS task log: logId 431; CIS report: cis-report-169474438-1782379290463.html
• Wiki signatures: debugnonhost-daemonset-write-conflict, linux-vhd-prgate-cis-ubuntu2204-gen2-containerd-6131-logfiles
• Repair item: https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38501652

[aks-node-assistant]

Failed gate run

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

Detective summary

Test_Ubuntu2204_HTTPSProxy_PrivateDNS/scriptless_nbc failed creating the VMSS while processing the CustomScript extension: CSE ExitCode=50, KubeletStartTime=n/a, and the known mandb/oldlocal cache pattern. Timeline and build status corroborate the E2E task exit code 1. A later ArtifactStreaming ARM64 scenario hit LocalDNS exporter failed-state, but the first/root signature is the HTTPSProxy CSE exit50 failure.

Likely cause and signature

Known HTTPSProxy PrivateDNS CSE/provisioning flake, signature ubuntu2204-httpsproxy-privatedns-cse-exit50-outbound-kubelet-na, confidence high. Strongest alternative is a LocalDNS exporter unit flake, but that occurred after the first failed scenario and is tracked separately under Bug #38581800.

Recommended owner/action

Continue the existing repair investigation in Bug #38559852; no PR author action is indicated from this evidence alone.

Evidence

• Task log: logId 538; job log: logId 545
• Wiki signature: ubuntu2204-httpsproxy-privatedns-cse-exit50-outbound-kubelet-na
• Repair item: https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38559852