Error: Failed to update deployment history. Error: Service Unavailable (CODE: 503)

Shyam Kulkarni 5 Reputation points
2023-02-13T11:34:40.73+00:00

My deployment is taking too much time due to
Error: Failed to update deployment history. Error: Service Unavailable (CODE: 503)
this takes 30+ minutes and then gives above error and then pass on.
User's image

facing this issue since few months any solution for this?

Log for reference :

2023-02-13T09:47:48.0259801Z Successfully added release annotation to the Application Insight : xxxxxxxxxxx-ai
2023-02-13T10:23:56.3581144Z ##[warning]Error: Failed to update deployment history. Error: Service Unavailable (CODE: 503)
Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
734 questions
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,579 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,152 questions
Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,332 questions
{count} vote

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 24,236 Reputation points Microsoft Employee
    2023-02-14T10:31:03.4733333+00:00

    @Shyam Kulkarni Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

    Based on the shared information, we have looked at the backend logs of your function app(asos-***-func) and we see that the deployment of function is failing with the error that there is no space left on device as shown below.

    "message":"OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545 caused: mkdir /mnt/data/docker/images/231072/aufs/mnt/9c04b/apmp: no space left on device: unknown"

    We have checked with Function app Engineering team, and they have confirmed that this is a known issue, and bug has been fixed and it is scheduled to rolled out in next release in few months. 

    As a workaround you need to scale up the function app from EP1 to EP2.

    Feel free to reach back to me if you have any questions on this.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.