actions / runner-images

GitHub Actions runner images
MIT License
9.32k stars 2.89k forks source link

pipeline failing with An error occurred while provisioning resources (Error Type: Failure). The remote provider was unable to process the request. #2575

Closed somiya9868 closed 3 years ago

somiya9868 commented 3 years ago

Description
The azure pipeline is failing with error

"An error occurred while provisioning resources (Error Type: Failure). The remote provider was unable to process the request."  

Area for Triage:

Question, Bug, or Feature?:
Bug

Virtual environments affected

Expected behavior
The pipeline should have executed with no issues.

Actual behavior
Suddenly few pipelines stopped running with the mentioned error.

Repro steps
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

  1. ran the pipeline with Image: ubuntu-latest
lashajala commented 2 years ago

Same West Europe

anderson-fachini commented 2 years ago

Same in Brazil with Ubuntu 16

paul-t-wright commented 2 years ago

What agent is everyone using? React to this comment:

Just trying to collate some info to see the severity of this outage in the absence of the status page saying anything. I'm not Microsoft or anything!

👍🏻 - macOS-10.14 👎🏻 - macOS-10.15 😄 - ubuntu-16.04 🎉- ubuntu-18.04 😕 - ubuntu-20.04 ❤️ - vs2017-win2016 🚀 - windows-2019

ubuntu-latest

nathanjhill1 commented 2 years ago

We are also having the same issue. We are in South Central US. We are using macOs-10.14

sanjay3290 commented 2 years ago

same issue in central us

warleyxavier commented 2 years ago

Same here 😕

KaiserZoza commented 2 years ago

same here :(

asehgalxom commented 2 years ago

This is has been closed so maybe no one is paying attention, I opened a new issue here. Everyone please try to raise that up

fbuzila commented 2 years ago

the same here:

[error]An error occurred while provisioning resources (Error Type: Failure).

,##[error]The remote provider was unable to process the request. Pool: Azure Pipelines Image: Ubuntu16

MattJeanes commented 2 years ago

Cheers for voting above everyone, according to the votes it looks like this is a complete worldwide outage across all agents 😨

This is a closed issue but it should still be sending notifications to maintainers, I recommend raising critical severity tickets on Azure support if this is severely impacting you to get some attention to this issue, nothing official yet. I've DM'd @AzureDevOps on Twitter for what it's worth but I am not severely impacted as it's out of work hours for us and we don't critically need them at the moment.

jason-e-gross commented 2 years ago

samesies

christianAtSuddath commented 2 years ago

yes:

##[error]An error occurred while provisioning resources (Error Type: Failure).
,##[error]The remote provider was unable to process the request.
Pool: Azure Pipelines
Image: windows-2019
Started: Just now
Duration: <1s
davidnarciso commented 2 years ago

Same here, Dev team blocked from builds :(

VikingHobo commented 2 years ago

Having the issue as well

ipeternella commented 2 years ago

Same thing here. Region: Brazil South.

sreepriyaks commented 2 years ago

same in Australia East since more than half an hour

goleafs commented 2 years ago

yep, same for us, East Canada ubuntu-latest no problems showing here - https://status.dev.azure.com/

sawaYch commented 2 years ago

Same. Region: East Asia Image: ubuntu-latest

SergioLTJ commented 2 years ago

Same problem here. Region: Brazil South.

christianAtSuddath commented 2 years ago

yep, same for us, East Canada no problems showing here - https://status.dev.azure.com/

Unbelievable!!!

evanwhitten commented 2 years ago

Same problem here "The remote provider was unable to process the request."

jsalmeida1101 commented 2 years ago

Same here

AlexandreMuskus commented 2 years ago

https://developercommunity.visualstudio.com/t/errorAn-error-occurred-while-provisi/1481083?space=21&ftype=problem&stateGroup=active&sort=newest

tessmanjonathan commented 2 years ago

Seeing the same problem across multiple different orgs

gmurched commented 2 years ago

same here, Brazil

SorenKlemmensen commented 2 years ago

Same issue. Region: Canada Central, vmImage: Windows-Latest

ssaric commented 2 years ago

Same here -> West Europe

praath commented 2 years ago

We are also experiencing this issue in a Build pipeline.

East US 2 Visual Studio version: latest

billybraga commented 2 years ago

https://developercommunity.visualstudio.com/t/errorAn-error-occurred-while-provisi/1481083?space=21&ftype=problem&stateGroup=active&sort=newest

There are other issues that were just created also:

https://developercommunity.visualstudio.com/t/Pipelines-unable-to-get-agent-from-MS-ho/1481067?space=21&q=%22The+remote+provider+was+unable+to+process+the+request%22

https://developercommunity.visualstudio.com/t/Pipeline-Build-on-Hosted-agent-fails-wit/1481043?space=21&q=%22The+remote+provider+was+unable+to+process+the+request%22

The problem is that there is not the place to report service availability issues:

image

https://docs.microsoft.com/en-us/azure/devops/user-guide/service-status-info?view=azure-devops#:~:text=report%20your%20issue%20using%20the%20Report%20a%20Service%20Availability%20Issue%20form

But there is no link to the Service Availability Issue form

MateusMo commented 2 years ago

Same here, Brazil

davidbirt commented 2 years ago

Same issue.

jdunnink commented 2 years ago

same issue here

kcherewyk commented 2 years ago

Same issue in western Canada

hosseinis commented 2 years ago

Same issue here from U.S.

ssay-work commented 2 years ago

same issue using a hosted agent in eastern us

jwyglendowski-precisionlender commented 2 years ago

image Looks like they are finally looking into it.

https://twitter.com/AzureDevOps/with_replies

davinomjr commented 2 years ago

Same issue

betabrandao commented 2 years ago

same issue in Brazil.

Qi-Jian-Huang-DevOps commented 2 years ago

Oh nice, I was trying to figure out what I did wrong for the past one hour, thought I broke something, ended up is something wrong from the hosted agent. Interesting.

Agent: windows-latest region: canada central

wggley commented 2 years ago

My fellow developers, maybe you are all trying to figure why I have called you here...

+1 Brazil

cricketthomas commented 2 years ago

same issue.

hilary-b commented 2 years ago

Same issue in Eastern US

alasdairmackenzie commented 2 years ago

They've updated the status page now https://status.dev.azure.com

christianAtSuddath commented 2 years ago

image

bcbeatty commented 2 years ago

https://status.dev.azure.com/_event/251790226

maikelvanhaaren commented 2 years ago

Fellow developer, what's your favorite programming joke?

Mine: Why Java developers have glasses? Because they can't see sharp. Ba dum tss..

betabrandao commented 2 years ago

image

Fellow developer, what's your favorite programming joke?

Mine: Why Java developers have glasses? Because they can't see sharp. Ba dum tss..

Skirtek commented 2 years ago

Fellow developer, what's your favorite programming joke?

Mine: Why Java developers have glasses? Because they can't see sharp. Ba dum tss..

SQL database walked into a NoSQL bar. A little while later he walked out, because he could not find a table :)

praath commented 2 years ago

We are also experiencing this issue in a Build pipeline.

East US 2 Visual Studio version: latest

This is resolved on my end.

sentimental37 commented 2 years ago

It started working for me image