I'm trying to configure continuous deployment for my Web App in Azure so it deploys every time I push an updated container image to the Azure registry.
However, when I go to "Container Settings" and set "Continuous Deployment" to true and then hit save I get the following error:
"Failed to update data for container settings."
I'm not sure how to start debugging this error message to find out what the issue is.
Does anyone have any ideas?
I faced the same error message when trying to update the configuration of a multi-container app.
The Azure portal sends the update as a request to their management API and the JSON response to this request contains a more detailed error message. This might help with debugging. For example, in my case the configuration was too long and this was kind of communicated in the response that I was able to find through the network tab of my browsers developer tools.
This just worked after revisiting the portal after a couple of days. Must have needed a bit of bedding in...
Related
Where are the errors located in the Azure portal GUI?
Abstract
I'm currently developing a Flask app, deploying it on Azure.
I've configured CI/CD with GitHub. Each push to the desired branch causes the thing to build.
There seems, however, to be a problem with this build that I need to discover.
Despite my great effort, despite reading a few pages of Azure docs and a few answers on this site, I cannot seem to find the actual location that would show me the Azure build errors I want to see.
What have I tried
Log Analytics
I've configured Log Analytics. I can't remember its function, but it was necessary to enable some logging.
GUI
I've checked the Logs tab for my AppService. Although I've noticed a few errors, these look as unhelpful as this:
If this is the most I would get, please note that in the comments.
Log Streaming
I've started streaming logs in VS Code. These only tell me that An unknown error has occurred. Check the diagnostic log for details.
Downloading logs from app's subdirectory
Although I cannot pin-point the exact article, there is a way of downloading logs from the app's endpoint. I did it, got two files and the most I would get is ERROR - Container for *app name* site *app name* is unhealthy, Stopping site.
Again, if this is meaningful for a rudimentary Flask app deployed in CI/CD pipeline with no tampering in the settings of Azure, let me know.
Wrapping up
Are the samples shown valid, meaningful errors? If not, where can I find more information?
I have tried to reproduce the issue by configuring an app with CI/CD using GitHub and integrated successfully as shown below:
if we made any changes in the repository then it will trigger a workflow and build process takes places.
If there are any errors then we can look at those errors in the github repository only by navigating to the Actions-->click on build, there you can see the errors as shown below:
You can also review the application logs, either by enabling diagnostic logging on app service to identify the cause or you can make use of application logs under (diagnose and solve problems--> availability and performance) from the portal under your web app.
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 am using the Devops release pipeline to deploy new releases to my function apps.
However a few days ago, the release pipeline stopped working and I continue to receive the following error message on deployments:
Error: Error: Failed to deploy web package to App Service. Bad Request (CODE: 400)
After digging in the kudu stack trace, I find the following:
Error occurred, type: error, text: No space left on device
However, when I look at my quota usage on the app service plan that hosts my function apps, I have not even exceeded 1% of my quota. I am on a basic app service plan that provides 10gb of storage and my function apps combined have used 50mib.
I am reaching out to see if anyone else has/is currently experiencing this issue and what they did to resolve it.
Many Thanks!
Adam
Some advice for trouble shooting:
You can use the Kudu service to see the size of all the files on the Azure. This way you can further check your storage. Go to Azure portal -> Your_APP_Service -> development tool -> advanced tool to access Kudu service and download the extension. You can click this blog for detailed information.
The issue may be that your source code and output are too large. In this case, try using a self-hosted agent and clear the cache.
The reason for the issue may also be that the packages uploaded at one time are too large, which leads to the shortage of temporary files. Click on the link to see if you have exceeded the temporary file limit.
I had the same problem, I connected with ssh to app service and run:
$ df -h
and scale up (App service plan)(be careful the server IP can change)
And after run the pipeline, Its run Correctly, if you wish you can return to the previous plan.
If anyone encounters this issue in the future this may resolve your problem.
I believe the problem with deployments may have been caused by a corrupt function app in the app service plan. I noticed that the function app I recently added had been categorised as a container although I never specified it as such. Anyway, deleting that function app and recreating it resolved the issue. All deployments to that app service plan are now working fine!
I have a working azure web app, I cant deploy anything when I click Deployment center it just stuck at Fetching deployment data
If I wait for while I get this:
I have to mention that I had apps before on azure and everything worked smooth.. the only difference between the apps is that the broken app I created with azure VS extension.
all the apps are configured to auto-deploy from Bitbucket
For me, there wasn't enough space on the disk. I saw this "lack of space" error message after clicking Deployments in Kudu (Advanced Tools in your web app). I deleted the LogFiles folder to free up space and everything went back to normal.
I had the same problem with deployment sticking/breaking when I was trying to use the F (free) tier. I was trying to push a .NET Core app with https: support enabled in the app. Because the F tier does not support SSL, it broke everything and there was no trace to say what the problem was. Not sure if this was your problem as well, but if anyone is trying to do the same thing that I did, I hope this is helpful. Changing to an S (standard) tier fixed it. I suppose disabling https: support in the app you are trying to push would work as well, but I did not try that approach.
This happened to me last night. Finished up some changes to an API and front end app. API published to app service without issue from Github pipeline. Front end app would not publish. Error was:
Deployment Failed with Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
Same issue as here. The deploument center would never load and eventually would give me a Gateway Timeout error. Two hours I spent trying to figure out what was wrong. Even opened a support ticket. It was a problem with the Azure service that was resolved by the next morning.
I'm trying to update a express web app and trying to connect VSTS source control to the same but I am getting the following error.
{"Code":"BadRequest","Message":"Repository
'UpdateSiteSourceControl' operation failed with
Microsoft.Web.Hosting.WebHostingException: AADSTS700027: Client
assertion contains an invalid signature." }
I had an express web app setup with VSTS and it was successfully connected with source control. I haven't changed anything but I am not sure what this error means. I was able to use Azure pipelines but I wasn't able to use "App Service build service" to connect to VSTS. I am not sure what am I doing wrong here. Any help would be appreciated.
This issue was related with an Azure update. They fixed it and the continuous integration via Kudu is working again.