search

Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82 stars 12 forks source link

Unable to edit or replace deployment #257

Open abaymar opened 6 years ago

abaymar commented 6 years ago

I'm creating a new deployment on a brand new resource group and I'm getting this:

"Unable to edit or replace deployment 'mesh_aras': previous deployment from '8/7/2018 1:36:24 PM' is still active (expiration time is '8/14/2018 1:36:23 PM'). Please see https://aka.ms/arm-deploy for usage details."

An only successful Mesh deployment I did before was a sample one, and that one was on a different resource group. "Mesh_aras" was never deployed.

Also I'm past that "expiration time" shown in the message.

What should I do next?

mikkelhegn commented 5 years ago

You can cancel the ARM deployment via PowerShell (https://stackoverflow.com/questions/32222691/cancelling-azure-resource-manager-deployment) or the portal also has a cancel button when you browse to the resource group.

abaymar commented 5 years ago

@MikkelHegn it's not about an old failed deployment. Every time that I try to create a new deployment on a brand new resource group, it fails for the _thisnew deployment:

C:>az mesh deployment create --resource-group al-arasMesh180919 --template-file C:\Examples\HelloMeshAttempt\mesh_rp.windows.json Deploying . . . Please provide string value for 'location' (? for help): eastus Unable to edit or replace deployment 'mesh_rp.windows': previous deployment from '9/19/2018 1:58:12 PM' is still active (expiration time is '9/26/2018 1:58:00 PM'). Please see https://aka.ms/arm-deploy for usage details.

mcollier commented 5 years ago

When I've encountered this issue. it appears to be related to a potential timeout setting with the az mesh deployment create CLI command (in my experience is about 10 minutes). If I wait longer, and check the Azure portal, the deployment eventually completes (~20-30 minutes).

Raag007 commented 5 years ago

Please change the file name and try to redeploy. I faced the same issue with file name: azuredeploy (17).json Solved by changing the filename to: azuredeploy.json

Thanks! Anuraag

anufryieu commented 5 years ago

Open target Resource Group on the azure portal, go to Deployment tab, find not completed deployments, cancel it, start new deploy and enjoy! :)

dastewa-zz commented 5 years ago

Thanks @Anufriev! That worked for me. Just a heads up that the deployment causing the question might not be in the resource group you think, depending on your template. The error message doesn't indicate where the problematic deployment is, so check a few other potential resource groups just in case!