Web App deployment failed "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

Question

Web App deployment failed "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

Allan Chong 5

When deploying a github repo from an external account, the web app deployment fails at Microsoft.web/sites/sourcecontrols with error code:"ResourceDeploymentFailure" and error message:"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

Even after disconnecting and reconnecting the github, the Web App's Deployment Center still states it hasn't deployed yet and receives the error "Request failed with status code: 401 under 'Fetching changes' activity".

Any help on this is much appreciated, thank you.

Allan Chong 5 Reputation points

2023-06-26T23:06:25.26+00:00

The github in question is a modification of this: https://github.com/Azure-Samples/cosmosdb-chatgpt

1 answer

Your answer

Allan Chong 5 Reputation points

2023-06-26T23:06:25.26+00:00

The github in question is a modification of this: https://github.com/Azure-Samples/cosmosdb-chatgpt

Answer 1

ajkuma 27,941 Microsoft Employee

@Allan Chong , Thanks for posting this question.

Firstly, apologies you're experiencing this issue.

Based on my understanding of your issue description- The error message "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed', typically indicates that there was an issue with the deployment process. This error can occur due to a variety of reasons, including issues with the GitHub repository, issues with the Azure Web App, or issues with the deployment process itself.

The error message "Request failed with status code: 401 under 'Fetching changes' activity" indicates that there was an authentication issue when fetching changes from the GitHub repository. This error can occur if the credentials used to authenticate with the GitHub repository are incorrect or have expired.

To isolate the issue, you may try the following steps:

1.Verify the GitHub repo ( that you shared) to ensure that it is accessible and that the credentials used to authenticate with the repository are correct.

Check the Azure Web App to ensure that it is properly configured and that there are no issues with the deployment process.

Additionally,

(If you haven't tried this already) - Try disconnecting and reconnecting the GitHub repository to the Azure Web App to see if this resolves the issue.
Review the deployment logs for the Azure Web App to see if there are any errors or issues that could be causing the deployment to fail.

Checkout the log directory/location info- Access log files -Enable and review logs to fetch more details about the error.

https://learn.microsoft.com/azure/app-service/troubleshoot-diagnostic-logs#access-log-files

Kindly let us know how it goes, I'll follow-up with you further.

Allan Chong 5 Reputation points

2023-06-27T20:49:51.9366667+00:00

Thank you for your response. We moved our code from Azure DevOps to a public git which has done the trick which indicates it was an authentication issue. We have no idea why the authentication didn't work because both the Web App deployment and the Azure DevOps are sitting in the same environment and using the same credentials.
ajkuma 27,941 Reputation points Microsoft Employee

2023-06-28T18:34:01.8+00:00

Allan Chong, Thanks for the follow-up and update. Glad to know that the issue is sorted out.

It's good to hear that moving your code to a public Git repository has resolved the issue. As you mentioned, it indicates that there was an authentication issue with the previous setup.

It is possible that the authentication issue was caused by a misconfiguration. It's also possible that there was an issue with the credentials or permissions that were being use. We may need additional info, to understand the issue more.

--
If the answer helped (pointed you in the right direction) > please click Accept Answer
Or please share the requested/more info to help you better.

清野剛史 5

I faced same error.

I found this in the log.

NuGet Config files used:
      D:\DWASFiles\Sites\#1pola-test3-web\AppData\NuGet\NuGet.Config
  
  Feeds used:
      https://api.nuget.org/v3/index.json
  
  Installed:
      82 package(s) to C:\home\site\repository\cosmoschatgpt.csproj
Done Building Project "C:\home\site\repository\cosmoschatgpt.csproj" (Restore target(s)).
Project "C:\home\site\repository\cosmoschatgpt.csproj" on node 1 (default targets).
C:\Program Files (x86)\MSBuild-16.4\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v8.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [C:\home\site\repository\cosmoschatgpt.csproj]

Deploy is failed because .NETFramework v8.0 were not found.

Please tell me how to fix it.

Share via

Web App deployment failed "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

1 answer

Your answer