Sorry, less a code issue but a process issue in deploying through Microsoft VSTS. I'm deploying an ARM template via a VSTS build definition and it failed (complaining the storage account was not in the same RG as the VM ).. BUT in the azure portal against the RG it shows a successful deployment and the resources deployed as expected.
What would cause VSTS to report an issue this way? Obvious issue is my deployment technically fails as a VSTS job despite being fine in Azure.
with no changes is stopped erroring so i'm guessing something on the azure side. Thanks anyway
Related
I have a release pipeline to deploy my ASP.NET MVC web app to Azure VM. I have configured the release pipeline and everything was working fine.
But all of a sudden, it started throwing the error shown here. I am using IIS Web App deployment tool for this in Azure DevOps:
Looks like it's been reported as an issue related to a new task versions for WebAppDeployment tasks. See here, you might find a workaround that will work for you: https://github.com/microsoft/azure-pipelines-tasks/issues/17634
I am trying to use Azure DevOps pipelines to build a .NET 5 (Core) web app and deploy it to my Azure app service. I can't find any complete examples in the documentation that achieve this so I'm following this:
https://github.com/shahedc/NetLearnerApp/blob/main/azure-pipelines.yml.txt
However, the Azure deploy task keeps returning this vague error:
In my Azure portal I only get this error:
I am assuming the issue is in my pipeline because deployment works when I deploy it directly from the Deployment Center in the Azure portal. Here are the details for the 3 relevant tasks my pipeline:
I found the solution. It turns out the issue was not in the pipeline, but was caused by a Git connection to the app service I had previously set up in the Azure Deployment Center. Even though I disconnected/removed this Git connection, there was somehow still a residual file left over in Azure that was causing the error. I deleted the 'deployments' folder in Kudu (pictured below) and the pipeline started working as expected.
Getting to the above pictured view:
Navigate to your Azure Function project
Search for Advanced Tools
Open PowerShell
Check if you have disk space available.
Yesterday we started getting this error, even if we tried to re-deploy packages that were successfully deployed just an hour before. Our system guys checked and found out that we reached the space limit and that it was time to upgrade.
P.S. I know that this was answered a long time ago. I am just sharing the solution that was not mentioned here and that worked for us.
think what Dan Beaulieu said in above answers is correct, but one thing to add, in my case, after deleting the deployments folder, remember to restart the app service/web app, which will make it take effect.
I have release azure function app from VSO Azure App Service Deploy release task,
it gives:
System.Nets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions I searched on google, people say the sockets get expired but i am using S3 pricing tier
I have then released the same function app from Visual Studio 2017 which runs perfectly fine without any exceptions.
I am attaching the artifacts, build assets, release pipeline details, please help. I will not be able to move to production unless this issue is resolved.
Structure of Artifacts which is not working
Structure of artifacts which is working fine-published from VS2017
Here is the github link for more details regarding the issue.
https://github.com/microsoft/azure-pipelines-tasks/issues/11345
I had to give a proper storage connection string for the following, instead of UseDevelopmentStorage=true,
I uploaded the pkg and confi in azure portal for deploying in staging environment and azure portal shows notification that 'Successfully started to deploy application...successfully started to deploy application to the staging environment for cloud service ...". There after no error or notification, neither the deployment ever visible/happen. What to look for? I looked into activity logs and there is operation
Write DeplymentSlot" with status Accepted.
There is a bug in the new Azure portal. It upload the faulty config file. If in the ACL the ip in quote "x.x.x.x" is replaced with "`x.x.x.x" (note the apostrophe after double quotes) then the new portal upload the file without any error but the deployment shows strange behavior. it notify successful deployment but actually nothing deployed. Also the deployment label got updated with one that actually failed to deploy. The old portal is come as rescue as it is able to catch the bug in first place. Hope Microsoft azure team will look into this.
Using VSO Team Project and Azure Web App.
I want to connect these services together, however, when I set up Continuous deployment it always fires this error:
My subscription is free DreamSpark.
What can I do?
Setting up CI with VSO TFS is not supported for Dream spark subs. It looks like we have a bug in the UI if you are getting this far.