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 Report - InternalServerError using ALZ Portal Accelerator #1775

Closed
SeanKelly35 opened this issue Sep 24, 2024 · 8 comments
Closed

Bug Report - InternalServerError using ALZ Portal Accelerator #1775

SeanKelly35 opened this issue Sep 24, 2024 · 8 comments
Assignees
Labels
bug Something isn't working Needs: External Changes ⚙️ When an issue/PR requires changes that are outside of the control of this repo Type: Upstream Dependency ⬆️ something must happen before start something else

Comments

@SeanKelly35
Copy link

SeanKelly35 commented Sep 24, 2024

Note from ALZ Core Team:

Important

Known issue in ARM, being resolved as we speak: see #1775 (comment)


Landing zone accelerator from the Microsoft Azure Training for AZ-305 is having issues completing the template correctly. I am getting an internal server error message. I followed the instructions precisely on this page: https://learn.microsoft.com/en-us/training/modules/cloud-adoption-framework-ready/6-deploy-blueprint

Yet I still get the error.
image

Explain with Copilot says to select a resource from the select a resource pane, I find a hidden resource and then it errors out saying there was still an internal server error.

image

Hoping to get some help so that I can continue my studies. Thanks.

@SeanKelly35 SeanKelly35 added the bug Something isn't working label Sep 24, 2024
@SeanKelly35
Copy link
Author

Here are the settings of my attempted landing zone accelerator deployment
image
image
image
image

@jdrepo
Copy link

jdrepo commented Sep 25, 2024

Same problem here, tried it in different tenants and with different settings and I always get after review + create validate the above mentioned "internal server error"

{"code":"InternalServerError","message":"Encountered internal server error. Diagnostic information: timestamp '20240925T062626Z', subscription id '', tracking id '8a909214-2339-43d2-8622-c7227ab8ce56', request correlation id '4e2ffe5b-98d9-447b-9466-502aaaa8b4e6'."}

image

image

Are there any further logs available where I can see what the problem for the internal server error is ?

@jtracey93 jtracey93 self-assigned this Sep 25, 2024
@jtracey93 jtracey93 added Needs: External Changes ⚙️ When an issue/PR requires changes that are outside of the control of this repo Type: Upstream Dependency ⬆️ something must happen before start something else labels Sep 25, 2024
@jtracey93
Copy link
Collaborator

Hey @SeanKelly35 & @jdrepo,

Thanks for reporting. We also noticed this to and have tracked this down to a bug in ARM that we are working closely with the engineering team to resolve.

We have identified the cause and are working out steps to remediate the rollout the changes to ARM ASAP.

For clarity this is not an issue with ALZ, and is impacting many other ARM/Bicep templates that use a particular nested deployment feature in a certain way. We understand this may be frustrating but we are working closely between the two teams to resolve as fast as possible.

Thanks for understanding

Jack

@jtracey93 jtracey93 changed the title Bug Report Bug Report - InternalServerError using ALZ Portal Accelerator Sep 25, 2024
@jtracey93 jtracey93 pinned this issue Sep 25, 2024
@jensdiedrich
Copy link

Hey @jtracey93

no problem at all, so I know that it has nothing to do with my tenant or subscription.
So I will go the ALZ-Bicep path

Regards

@SeanKelly35
Copy link
Author

Thanks so much for getting back to me. I can wait for a bit. Cheers!

@jtracey93
Copy link
Collaborator

Hey @jensdiedrich @SeanKelly35 @jdrepo

This has now been fixed and rollout was made overnight, and we have tested and all working :)

@jdrepo
Copy link

jdrepo commented Sep 26, 2024

Hey @jtracey93 , thanks for the notification, yes now it seem that I can get over the review + create step and the deployment starts now. But now I have an issue with the single subscription scenario. Will open another issue

@SeanKelly35
Copy link
Author

@jtracey93 Thanks a bunch will give it a try later today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs: External Changes ⚙️ When an issue/PR requires changes that are outside of the control of this repo Type: Upstream Dependency ⬆️ something must happen before start something else
Projects
None yet
Development

No branches or pull requests

4 participants