Azure - Bicep deployment DeploymentActive - Unable to edit or replace deployment

Matthew Lee 0

Hi, I'm seeing this error daily when deploying Bicep from Azure DevOps. {"customHtml":{"htmlTemplate":"<code><div><div>Unable to edit or replace deployment 'config1740623100': previous deployment from '2/28/2024 2:25:03 AM' is still active (expiration time is '3/6/2024 2:25:02 AM'). Please see <a target="_blank" class="msportalfx-ext-link" href="https://aka.ms/arm-deploy-resources">https://aka.ms/arm-deploy-resources</a> for usage details.</div></div><div><div>Unable to edit or replace deployment 'deployment-1740623100-uksouth': previous deployment from '2/28/2024 2:25:03 AM' is still active (expiration time is '3/6/2024 2:25:02 AM'). Please see <a target="_blank" class="msportalfx-ext-link" href="https://aka.ms/arm-deploy-resources">https://aka.ms/arm-deploy-resources</a> for usage details.</div></div></code>","viewModel":null}} CLI Tasks example Timestamp:

          - powershell: |
              $timestamp =  Get-Date -Format "yyyyMMddTHHmmssss"
              Write-Host "##vso[task.setvariable variable=timestamp;isoutput=true]$timestamp"          
            name: setTimestamp

Deployment:

          - task: AzureCLI@2
            inputs:
              azureSubscription: '${{ parameters.SubscriptionConnectionId }}'
              scriptType: 'bash'
              scriptLocation: 'inlineScript'
              workingDirectory: $(System.ArtifactsDirectory)
              inlineScript: |
                az deployment group create \
                  --name $(setTimestamp.timestamp) \
                  --resource-group ${{ parameters.ResourceGroup }} \
                  --template-file ${{parameters.TemplateRelativeFileLocation}} \
                  --parameters ${{parameters.ParametersRelativeFileLocation}} ${{parameters.OptionalArguments}}

Bicep snippet example:

module  storageAccount '../storage/storage-account.bicep'  =  {
  name: 'deployment-${convertedEpoch}-${location}'

How can i resolve this issue? I'm using unique deployment names for the az cli and also, unique module names. Kind regards Matt

KarishmaTiwari-MSFT 19,782 Reputation points Microsoft Employee

2024-02-28T20:42:50.8166667+00:00
@Matthew Lee Thanks for posting your query on Microsoft Q&A.

The error message states: “Unable to edit or replace deployment ‘config1740623100’: previous deployment from ‘2/28/2024 2:25:03 AM’ is still active (expiration time is ‘3/6/2024 2:25:02 AM’).” This means that a deployment with the same name (‘config1740623100’) is currently in progress or hasn’t been completed yet. To resolve this, you have a few options:

Wait for Completion or Failure:

If the previous deployment is still running, you can wait for it to complete or fail. Once it finishes, you can retry your deployment.

Keep in mind that deployments have an expiration time (in this case, until ‘3/6/2024 2:25:02 AM’). After that, they will automatically be considered completed.

Cancel the Active Deployment:

Go to the Azure portal.

Choose the resource group related to your deployment.

Under the settings, find the “Deployments” section.

Locate the running deployment (‘config1740623100’) and either cancel or restart it.

Unique Deployment Names:

Ensure that each deployment has a unique name. If you’re using Bicep templates, make sure that modules or resources within the template do not share the same name.

You can also manually delete the active deployment from the command line using Azure CLI or PowerShell.

Let me know the results.
Matthew Lee 0 Reputation points

2024-02-29T07:23:15.5+00:00

Thanks for your response. The options that you have stated are not suitable for an automated environment. Even when the deployments have been successful, they take a week to expire, which blocks subsequent deployments (which have unique deployment names). What is the root cause of this issue? Can deployment expiry be shortened?
KarishmaTiwari-MSFT 19,782 Reputation points Microsoft Employee

2024-03-04T04:32:36.62+00:00

@Matthew Lee Did you get a chance to send me an email as requested via private message. Please do so if you are still seeing this issue. Thanks.

Share via

Azure - Bicep deployment DeploymentActive - Unable to edit or replace deployment

Your answer