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.

Sign up for GitHub

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

Jump to bottom

Multiple ALZ portal accelerator deployment fail in same AAD Tenant - Bug Report #1077

Closed
JefferyMitchell opened this issue Oct 11, 2022 · 2 comments · Fixed by #1078
Closed

Multiple ALZ portal accelerator deployment fail in same AAD Tenant - Bug Report #1077

JefferyMitchell opened this issue Oct 11, 2022 · 2 comments · Fixed by #1078
Assignees
@jtracey93
Labels
bug Something isn't working engineering engineering work enhancement New feature or request Status: Fixed

Comments

@JefferyMitchell
Copy link
Contributor

JefferyMitchell commented Oct 11, 2022 •
edited by jtracey93
Loading

Describe the bug When deploying ALZ multiple times in the same AAD Tenant deployments fail with "conflict" in deployment operations due to having the same deployment name. This can also be observed with the ALZ Bicep reference implementation. Steps to reproduce

  1. Portal - "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.", 

    "details": [
    {
        "code": "Conflict",
        "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"DeploymentFailed\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details.

Screenshots 2. MicrosoftTeams-image (10)

Possible solution-
1.) Deploying to the same region for all lab/demo users? 2.) Create unique deployment names that are random enough to support 5-600 deployments at the same time?

@JefferyMitchell JefferyMitchell added the bug Something isn't working label Oct 11, 2022
@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Oct 11, 2022
@jtracey93 jtracey93 self-assigned this Oct 11, 2022
@jtracey93
Copy link
Collaborator

Okay so looking into portal now.

But ALZ-Bicep will be fixed by PR: Azure/ALZ-Bicep#312 as related to issue Azure/ALZ-Bicep#267

@jtracey93 jtracey93 added enhancement New feature or request engineering engineering work and removed Needs: Triage 🔍 Needs triaging by the team labels Oct 11, 2022
@jtracey93 jtracey93 mentioned this issue Oct 11, 2022
Merged
6 tasks
@jtracey93
Copy link
Collaborator

Have raised PR to fix in #1078

@ghost ghost added the Status: Fixed label Oct 12, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jtracey93 jtracey93

Labels
bug Something isn't working engineering engineering work enhancement New feature or request Status: Fixed
Projects
None yet
Milestone
No milestone
2 participants
@JefferyMitchell @jtracey93