-
Notifications
You must be signed in to change notification settings - Fork 981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: PowerShell deployment runs forever or fails #1793
Comments
@jdrepo I'm busy testing the release of Policy Refresh and have had many issues today. I don't think it's a PowerShell issue, looks like the ARM engine is throttling or having issues. Can I ask you to try again after a bit? There is some another issue currently impacting testing that we're investigating - its authentication related. |
@Springstone Thanks for your reply, yes I can test it again later, I also had the problem yesterday and I also think it has nothing to do with PowerShell, as the problem also occurs with azure cli deployments, so then probably a fundamental problem with the ARM backend |
@jdrepo are you still experiencing issues or can we close the issue? |
Hi @Springstone |
Hi @Springstone, tried again today and the issues still occur, seems to me nothing has changed, deployment runs forever if deploying with PowerShell |
@jdrepo could you try run the same deployment without the -WHATIF (we suspect recent changes in pre-flight processes are causing a problem) - or try running again with the latest release of ALZ.
If I run the above it succeeds, takes about 60 seconds. |
@Springstone Will give it another try, it seems to me that it depends on the template parameter file, i just tried it with a "small" parameter file with only the |
@Springstone Did some more tests and I think found the cause: If I change the deployment location to another region than I did a test with Can you try to run your last deploynment against the |
@jdrepo yes, looks like it is |
@Springstone yes, I can observe the same behaviour. PowerShell hangs and can´t be terminated. I let the task running and after approx. 1 hour it came back with a lot of error messages I have no idea why the Earlier this morning I tried it against the I can try to open a support ticket but I don´t know if this environment is covered by a support plan... `DEBUG: ============================ HTTP RESPONSE ============================ Status Code: Headers: Body: DEBUG: 11:33:42 - [ResourceManagerCmdletBase.ExecuteCmdlet] Caught unhandled exception: Microsoft.Rest.Azure.CloudException: |
@jdrepo not to worry, I've opened an internal engineering ticket to investigate the WHATIF issue. However, I do believe that if you remove the WHATIF flag the deployment will proceed/succeed. If you find otherwise, please do let me know. |
@Springstone yes as assumed the "real" deployment does start, so it´s indeed only an issue with --whatif deployments.
|
@jdrepo any errors that include the text TLDR Policy isn't available for assignment yet. If you re-run the deployment with the same parameters, it will succeed. |
@Springstone can you give me short notice how and if I can extend deployment wait time ? For the what-if issue: |
@jdrepo you can't change the wait time yourself, but we've pushed through a patch to increase the wait time an additional couple of minutes, use the latest release (https://github.com/Azure/Enterprise-Scale/tree/2024-10-14). I am working with engineering on the WHATIF issue but seems something has changed as it suddenly started working this morning. Could you confirm that it is working for you? |
@Springstone isn'it possible to change the wait time if I modify the parameter "delayCount" in the template parameter file ? Did another WHATIF deployment against the "westeurope" region and the issue still occurs ? |
@jdrepo yes, you can increase the I've confirmed with PG this is a transient issue, which is why it sometimes works and sometimes doesn't (very inconsistent). I ran this on the weekend and 9/10 worked fine, one time it failed with a similar error. I wouldn't worry about the SwitzerlandNorth, as it could be that an RP or part of ARM is running from there - the error message doesn't indicate an actual issue with deployment, just that it's a long running operation (basically it's timed out). |
Describe the bug
Deploy ALZ reference implementation with PowerShell doesn´t work
Steps to reproduce
New-AzTenantDeployment -Name "ALZ-Deployment-$(Get-Date -Format 'yyyyMMddTHHMM')" -Location "westeurope" -TemplateUri "https://raw.githubusercontent.com/Azure/Enterprise-Scale/2024-09-03/eslzArm/eslzArm.json" -TemplateParameterFile ".\ALZ-Portal-parametersFile.json" -WhatIf
Getting the latest status of all resources...
foreverSeems to me that there is the same error/behaviour in the "Test Portal experience" workflow in this repo ?
Screenshots
Is this a general problem with PowerShell deployment at the moment ?
The text was updated successfully, but these errors were encountered: