Create Artifact Container failed: Artifact storage quota has been hit. Unable to upload any new artifacts #128968
Unanswered
neelDeveloper97
asked this question in
Actions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
I am facing an error while deploying my node server to azure.
heres the action logs which I am getting:
Artifact name is valid!
Create Artifact Container - Error is not retryable
Begin Diagnostic HTTP information
Status Code: 403
Status Message: Forbidden
Header Information: {
"content-length": "333",
"connection": "close",
"content-type": "application/json; charset=utf-8",
"date": "Tue, 18 Jun 2024 13:26:53 GMT",
"server": "Kestrel",
"cache-control": "no-store,no-cache",
"pragma": "no-cache",
"strict-transport-security": "max-age=2592000",
"x-tfs-processid": "512XXXXX",
"activityid": "XXXX",
"x-tfs-session": "XXXX",
"x-vss-e2eid": "XXXX",
"x-vss-senderdeploymentid": "XXXXX",
"x-frame-options": "SAMEORIGIN"
}
End Diagnostic HTTP information
Begin Diagnostic HTTP information
Status Code: 403
Status Message: Forbidden
Header Information: {
"content-length": "333",
"connection": "close",
"content-type": "application/json; charset=utf-8",
"date": "Tue, 18 Jun 2024 13:26:53 GMT",
"server": "Kestrel",
"cache-control": "no-store,no-cache",
"pragma": "no-cache",
"strict-transport-security": "max-age=2592000",
"x-tfs-processid": "XXXXX",
"activityid": "XXXX",
"x-tfs-session": "XXXX",
"x-vss-e2eid": "XXXX,
"x-vss-senderdeploymentid": "744dbee7-4a20-affb-6b9b-ecd612b3b335",
"x-frame-options": "SAMEORIGIN"
}
Error: Create Artifact Container failed: Artifact storage quota has been hit. Unable to upload any new artifacts
Things I have tried:
Clearing various of the previous workflows/artifacts and logs to clean up the space for the quota.
Verified that I have all the required permissions.
Created a new repo with new azure instance for deployment (still same error there)
Upgraded my plan in Azure
Is there any other way to fix this issue? Please do let me know I am stuck with an urgent deployment.
Beta Was this translation helpful? Give feedback.
All reactions