Azure/bicep-registry-modules

[Failed pipeline] avm.res.network.express-route-gateway

Closed this issue · 3 comments

avm-team-linter commented

Important

@Azure/avm-res-network-expressroutegateway-module-owners-bicep, the workflow for the avm/res/network/express-route-gateway module has failed. Please investigate the failed workflow run. If you are not able to do so, please inform the AVM core team to take over.

microsoft-github-policy-service commented

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

arnoldna commented

Error:
11:19:34 - The deployment 'a-r-n-erg-max-t3-20240612T1106281675Z' failed | with error(s). Showing 2 out of 2 error(s). Status Message: The current | operation could not be executed because it is already in progress. | (Code: ConflictError) Status Message: At least one resource | deployment operation failed. Please list deployment operations for | details. Please see https://aka.ms/arm-deployment-operations for usage | details. (Code: DeploymentFailed) - The resource write operation | failed to complete successfully, because it reached terminal | provisioning state 'Failed'. (Code: ResourceDeploymentFailure) - The | current operation could not be executed because it is already in | progress. (Code: ConflictError) CorrelationId: | 69548b6d-898c-4ecc-b3f7-40f8dde1390e

Existing resource was already being deployed.