OfficeDev / microsoft-teams-apps-icebreaker

Icebreaker is an open-source app for Microsoft Teams that helps the whole team get closer by pairing members up every week at random to meet for coffee, burgers, pizza, or a walk around the block.
MIT License
174 stars 206 forks source link

DeploymentFailed - Conflict #260

Closed markp022 closed 2 years ago

markp022 commented 2 years ago

Hi, we are trying to redeploy the app to resolve some that occurred during a previous installation.

We are following https://github.com/OfficeDev/microsoft-teams-apps-icebreaker/wiki/Deployment-Guide-manual for the installation.

It looks like there is something remaining from a previous installation, that is now blocking the new installation. How can we find out what it is, and delete it?

The error we're getting is: Your deployment failed Resource: ice-breaker-.../web (Type=Microsoft.Web/sites/sourcecontrols, Status=Conflict) "error": { "code": "DeploymentFailed", "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 }\r\n}" } ] },

The cleanup we did:

My account has the global admin role, and the co-owner role on the subscription. We did take a look at this issue: https://github.com/OfficeDev/microsoft-teams-apps-icebreaker/issues/256 There are a few differences:

gsv022 commented 2 years ago

Hi @markp022 , Thanks for raising the issue. We will look into this and get back to you soon.

gsv022 commented 2 years ago

Hi @markp022 , Could you please re-sync the app service(microsoft.web/sites) again.

Thank you

markp022 commented 2 years ago

Thank you for your help. The Sync option was not available, because the App Service was not deployed due to the deployment failure.

I started a new deployment at a quiet time in our Azure region, and this time it worked without an error. The other thing I did different was explicitly set the Tenant Id in the custom template form.

Hopefully this will help someone else in the future: