-
Notifications
You must be signed in to change notification settings - Fork 39
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: Pipeline failure at What If stage #254
Comments
Hi @astallabrass, apologies for the delay. Can you please check in your mgmt repo if the value for The what-if operator can be somewhat finicky at times, although this one seems a bit different than normal. |
Hi @oZakari, I can confirm they are the same "rg-alz-connectivity" Thanks Aaron |
Hi @astallabrass, I was able to replicate this issue. It does appear to be an issue with the what-if operator. If I extend the retry count past 10, it will occasionally work as anticipated. When I actually deploy the resource group using the pipeline and then run the what-if afterwards I have not come across any issues with the what-if operator working. I do know the Azure Bicep team is working on improving the what-if functionality and usability. However, for the time being, I am going to update the workflow to skip the what-if on the first deployment for the networking deployments. |
Thanks for the update @oZakari 👍 |
Is there an existing issue for this?
Infrastructure as Code Type? (Required)
bicep
PowerShell Module Version (Optional)
No response
Bootstrap Module Version (Optional)
No response
Starter Module? (Required)
bicep - complete
Starter Module Version (Optional)
No response
Input arguments of the ALZ-PowerShell-Module (Optional)
No response
Debug Output/Panic Output (Optional)
Expected Behaviour (Required)
Looking to deploy the new version of the ALZ structure that has no custom configuration at this time, as focussed on seeing how the deployment pans out.
Actual Behaviour (Required)
When executing the "01 Azure Landing Zones Continuous Integration" pipeline, the job is failing at point of Whatif Deploy with Bicep. The Hub (Hub-and-Spoke) Multi-Region Deployment job indicates that it can't find the resource group "rg-alz-connectivity" in the connectivity subscription. It retries 10 times before failing the job completely.
Given this is running in WhatIf mode, should it be failing at this stage given nothing is deployed as yet?
Steps to Reproduce (Optional)
No response
Important Factoids (Optional)
I have attempted to create the resource group manually but still it is failing.
First time performing this deployment so appreciate that we may have missed something here as would've expected to see this in an already raised issue. Or whether its solely down to the multi-region deployment that differs to the single.
References (Optional)
No response
The text was updated successfully, but these errors were encountered: