{AKS} Fix remaining CLI Runner test failures

[FumingZhang]

🤖 PR Validation — ️✔️ All clear

Breaking Changes	Tests
️✔️ None	️✔️ 130/130

Related command

az aks

Description

Fix the actionable failures observed in CLI Runner run 0c9345bc-24dd-493a-bab5-1ddce36bf31a:

• pass the Container Insights solution JSON through a registered scenario kwarg so the live retry adapter does not interpret JSON braces as str.format placeholders;
• initialize the Container Insights solution before the monitoring-addon MSI scenario creates its cluster, avoiding DCR creation before workspace tables exist;
• wait for the cluster to settle between sequential VirtualMachines nodepool autoscaler operations, while keeping those additional requests out of cassette replay.

Artifact Streaming and Control Plane Metrics scenarios remain enabled. AKS RP investigation found that their failures reflect API-version and deployed-toggle rollout issues rather than deprecated features.

Testing Guide

AZURE_CONFIG_DIR=/tmp/clean-config VIRTUAL_ENV=/workspace/aenv \
  /workspace/aenv/bin/azdev test acs --no-exitfirst

Result: 980 passed, 84 skipped, 4 subtests passed.

VIRTUAL_ENV=/workspace/aenv /workspace/aenv/bin/azdev style acs

Result: pylint and flake8 passed.

The exact Python 3.12/3.14 CI failure was also reproduced and verified with:

python -m pytest -q \
  src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_aks_provisioning_retry.py \
  src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_aks_commands.py::AzureKubernetesServiceScenarioTest::test_aks_create_autoscaler_then_update_vms_pool

Result: 30 passed, 5 subtests passed.

History Notes

None. Test-only changes.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Yong Zhang (yonzhan)]

AKS

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[Copilot]

Pull request overview

This PR updates AKS scenario tests to address remaining CLI Runner live-test failures by avoiding accidental str.format interpolation of inline JSON, ensuring prerequisite Container Insights resources exist before cluster creation, and adding waits to reduce flakiness between sequential nodepool autoscaler operations.

Changes:

• Pass the Container Insights solution JSON via a registered kwargs placeholder ({container_insights_solution}) instead of embedding JSON directly in the formatted command string.
• Create the Log Analytics workspace/solution before running the MSI monitoring-addon cluster create, and pass --workspace-resource-id.
• Add az aks wait --updated calls between sequential VirtualMachines autoscaler/nodepool operations.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_aks_provisioning_retry.py	Adds a unit test asserting Container Insights solution JSON is passed via a registered scenario kwarg (not inlined into the command string).
src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_aks_commands.py	Updates live scenario logic to use kwarg-based solution JSON, pre-create workspace for monitoring-addon MSI scenario, and adds waits between autoscaler operations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).