Deploy issue

[microsoft]

Deploy issue

[gracez72]

Hi, thanks for raising the issue! Do you have error details for the template deployment and was this deployed using the Deploy to Azure button in the dev branch?

[gracez72]

Adding any errors/details here on this issue would be great so others can also refer to it if they get similar errors! The server_farm_id refers to the Azure App Service Plan and is usually in the following format: /subscriptions/{app_service_plan_subscription_id}/resourceGroups/{resource_group_name}/providers/Microsoft.Web/serverfarms/{app_service_plan_name}
We are currently still editing the deploy to azure process and will update the documentation and input names so that is more clear.

The 'DatabaseAccount name already exists' error may be because a previous deploy attempt successfully created the cosmosDB. If you check under the 'Deployments' header in the resource group, creating a new cosmosDB might have failed because it was already deployed before, but the other resources should be able to use the existing database account and successfully deploy.

[viperfx]

I didn't see any error details. Where would I look to find that? Yes I was using the dev branch using deploy button

…

On Mon., Apr. 20, 2020, 16:21 Grace Zhang, ***@***.***> wrote: Hi, thanks for raising the issue! Do you have error details for the template deployment and was this deployed using the Deploy to Azure button in the dev branch? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACQEQI3H7OF3MBF6WWHUG3RNSVELANCNFSM4MLR4BGQ> .

[gracez72]

If you click deploy after using the button, there should be a link next to the "Deployment Failed" message that says "View Error". If you click that link, there should be a popup that gives the error details. If that doesn't provide any additional details, you can also go to the Azure portal and to the resource group that you are attempting to deploy to. There should be header called "Deployments" under "Settings" on the left side navigation bar, and if you click it, it will provide a summary of which resources failed to create and a link to "Operation details", which provide detailed summaries of why the particular resource failed.

[viperfx]

Just tried that, and all the past event are success. Will try deploy again and see what happens.

[viperfx]

One doubt I had - when I create a App Service Plan - should the OS be linux or windows?

[viperfx]

Ive tried it again, and no further details were given. When I click View Error, a similar message to the one at the top is provided.

Ive checked deployments and there are no entries for the deployment showing up in the resource group I selected.

[gracez72]

The OS for the App Service Plan should be linux! Another thing you could try if you use Powershell and have the tracking id from the message, is to run Get-AzLog -CorrelationId xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -DetailedOutput, this should provide the detailed error messages. I will try to deploy using the button as well and see if I run into similar issues.

[viperfx]

Okay. Would you like me to put the return here? or shall I send it to your team via email? Do you have a dev team alias I can reach out on?

[viperfx]

It looks like the main error is "The specified app service plan was not found."

Can you confirm the instructions for how to set the server_farm_id

PS - The input labels are very confusing and the documentation on some fields and where to get them are missing.

[viperfx]

Managed to get past when I changed the region.

Deploying started .. up to "Updating Microsoft.DocumentDB/databaseAccounts"

Failed with this error

DatabaseAccount name 'acms-cosmos' already exists. ActivityId: 86fcf2bb-5c92-409e-beb5-0cb232436d0f, Microsoft.Azure.Documents.Common/2.10.0

[viperfx]

I have checked and there is no Cosmos DB that exists with that name.

{
  "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": "BadRequest",
      "message": "{\r\n  \"code\": \"BadRequest\",\r\n  \"message\": \"DatabaseAccount name 'acms-cosmos' already exists.\\r\\nActivityId: f1dea428-3802-4c2d-8b6f-f3cc8c8d11ad, Microsoft.Azure.Documents.Common/2.10.0\"\r\n}"
    }
  ]
}

[viperfx]

I had to deploy it, to let it fail, then edit the template manually so I can change the database name in the variables. I redeployed, and the cosmosDB was created. Everything was running, but when I went to the site I get ":( Application Error". Clearly there are quite a few bugs, and I think I will let the project mature a bit before I try again.

[gracez72]

Thank you for the comments, I will fix the CosmosDB bug and update the documentation with the issues that you ran into. I have encountered "Application Error" before and I was able to fix it by restarting the Azure App Service, but I'll test the deployment process again and document any fixes to errors I encounter.

[viperfx]

Just an update - I was able to make the deploy "successfully"

But got the following when visiting the site:

[viperfx]

Is there any updates on this issue?