DeploymentNotFound on subscription-scope deployments with infra.layers (azd 1.24.3)
Output
azd 1.24.3 (commit f5327208), az 2.85.0, macOS arm64, public cloud.
azure.yaml uses infra.layers (two layers, both targetScope = 'subscription'):
infra:
provider: bicep
layers:
- { name: base, path: infra, module: main }
- { name: sli, path: infra/sli, module: main }
Observed
Two DeploymentNotFound failures across 12 runs, on different code paths:
-
azd down (void POST path)
ERROR: deleting infrastructure: ... deploying empty template to subscription:
DeploymentNotFound: Deployment '<name>' could not be found.
-
azd up (provision polling) — second layer, ~28s after submit:
ERROR: error executing step command 'provision sli': ... deploying to subscription:
DeploymentNotFound: Deployment '<name>' could not be found.
In both cases, az deployment sub show --name <name> returned provisioningState: Succeeded for the same name, with correlationId matching the TraceID azd printed.
Expected
Either azd's view matches ARM (no 404), or — if the 404 is real — the subsequent ARM record should not be Succeeded.
Frequency
12 runs (6 × azd up, 6 × azd down), 2 failures (~17%).
Notes
DeploymentNotFoundon subscription-scope deployments withinfra.layers(azd 1.24.3)Output
azd 1.24.3(commitf5327208),az 2.85.0, macOS arm64, public cloud.azure.yamlusesinfra.layers(two layers, bothtargetScope = 'subscription'):Observed
Two
DeploymentNotFoundfailures across 12 runs, on different code paths:azd down(void POST path)azd up(provision polling) — second layer, ~28s after submit:In both cases,
az deployment sub show --name <name>returnedprovisioningState: Succeededfor the same name, withcorrelationIdmatching theTraceIDazd printed.Expected
Either azd's view matches ARM (no 404), or — if the 404 is real — the subsequent ARM record should not be
Succeeded.Frequency
12 runs (6 ×
azd up, 6 ×azd down), 2 failures (~17%).Notes
DeployToSubscription), not the void path.azd-issue-attachments.zip(≈ 100KB).