Skip to content
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

Open
1 task done
astallabrass opened this issue Nov 22, 2024 · 5 comments
Open
1 task done

Bug: Pipeline failure at What If stage #254

astallabrass opened this issue Nov 22, 2024 · 5 comments
Assignees
Labels
Needs: Attention 👋 Needs attention from the maintainers Status: In PR 👉 This is when an issue is due to be fixed in an open PR Type: Bug 🪲 Something isn't working

Comments

@astallabrass
Copy link

astallabrass commented Nov 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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

@astallabrass astallabrass added Needs: Triage 🔍 Needs triaging by the team Type: Bug 🪲 Something isn't working labels Nov 22, 2024
@jaredfholgate
Copy link
Member

@oZakari and @sebassem Is this something you can check? Thanks

@oZakari oZakari self-assigned this Nov 23, 2024
@oZakari
Copy link
Contributor

oZakari commented Dec 6, 2024

Hi @astallabrass, apologies for the delay. Can you please check in your mgmt repo if the value for CONNECTIVITY_RESOURCE_GROUP config/custom-parameters/resourceGroupConnectivity.parameters.all.json has the same value as parResourceGroupName in the parameters.json?

The what-if operator can be somewhat finicky at times, although this one seems a bit different than normal.

@oZakari oZakari added Needs: Author Feedback 👂 Needs the author to provide feedback and removed Needs: Triage 🔍 Needs triaging by the team labels Dec 6, 2024
@astallabrass
Copy link
Author

Hi @oZakari, I can confirm they are the same "rg-alz-connectivity"

Thanks

Aaron

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 Needs attention from the maintainers and removed Needs: Author Feedback 👂 Needs the author to provide feedback labels Dec 6, 2024
@oZakari
Copy link
Contributor

oZakari commented Dec 10, 2024

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.

@astallabrass
Copy link
Author

Thanks for the update @oZakari 👍

@jaredfholgate jaredfholgate added the Status: In PR 👉 This is when an issue is due to be fixed in an open PR label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Attention 👋 Needs attention from the maintainers Status: In PR 👉 This is when an issue is due to be fixed in an open PR Type: Bug 🪲 Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants