search

Azure / deployment-stacks

Contains Deployment Stacks CLI scripts and releases
MIT License
87 stars 6 forks source link

Delays in deployments appearing in Portal #77

Closed slavizh closed 1 year ago

slavizh commented 1 year ago

Describe the bug I am seeing delays in deployments appearing in portal again when using deployment stacks. For example I had deployment stacks failure like:

New-AzSubscriptionDeploymentStack: 10:12:19 - The deployment 'lz-analysis-services-monitoring' failed with error(s). Showing 3 out of 3 error(s).
Error: Code=DeploymentStackUpdateFailed; Message=One or more stages of the deploymentStack failed. Correlation id: '1d58bde5-82f0-4637-892b-07ca323cfb7b'

Error: Code=DeploymentFailed; Message=At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.

Error: Code=DeploymentFailed; Message=At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.

To Reproduce Steps to reproduce the behavior:

  1. Deployment stacks fails
  2. It produces deployment ID
  3. I go to Portal and under the subscription where the deployment stacks is deploying the deployment I cannot find it. image

I even waited 5-10 minutes but without any result.

Expected behavior Deployment to be visible.

Repro Environment Host OS: Windows 11 Powershell Version: 7.3.1

Server Debugging Information Correlation ID: 1d58bde5-82f0-4637-892b-07ca323cfb7b Tenant ID: I can provide in private Timestamp of issue (please include time zone): above, Eastern Europe Time zone Data Center (eg, West Central US, West Europe): West Europe

Additional context Add any other context about the problem here.

dantedallag commented 1 year ago

Thanks for pointing this out. Currently, subscription scoped stacks are not going to show up in the portal under Deployments. This is being addressed and we will leave this open until fixed.

slavizh commented 1 year ago

Just to clarify. I am not asking Deployment Stacks to be visible in Deployments views. I am asking the deployment that Deployment stacks creates to be visible in Deployments. Such bug existed in the previous preview and it should have been fixed. If I remember it was suppose to be fix on the deployment engine rather on the cmdlets. It is strange that this bug was suppose to be fixed in previous preview and now it appears again.

snarkywolverine commented 1 year ago

The deployment should show up eventually; unfortunately, the lag time is measured in hours, not minutes. The investments required to shorten this lag time are still ongoing.

slavizh commented 1 year ago

ok. I hope this gets priority to fix as it turns the whole thing with errors event bigger nightmare than currently it is.

snarkywolverine commented 1 year ago

This is now resolved.