actions / runner-images

GitHub Actions runner images
MIT License
9.17k stars 2.84k 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
andy-mishechkin commented 3 years ago

Hello, @somiya9868 May you provide link to failed pipeline, please

miketimofeev commented 3 years ago

@somiya9868 there was an issue with the backend service, which is resolved by now. Sorry for the inconvenience. I'm going to close the issue, but please feel free to contact us if you have any concerns. Thank you!

mottykohn commented 2 years ago

I'm having same issue right now. I checked https://status.azure.com/en-us/status/ and there is no indication of anything being down

MattJeanes commented 2 years ago

Yep same issue here, I just made a big config change so I thought I broke something 😁

By the way Azure DevOps status page is here: https://status.dev.azure.com/ but nothing yet

sentimental37 commented 2 years ago

Yes, for me as well, just finished some quick changes, and tried building the branch, but got a build canceled email. Nothing updated on the Azure status page.

Aaronmyster commented 2 years ago

Also having the same issue right now.

jessebacon commented 2 years ago

Same issue

##[error]An error occurred while provisioning resources (Error Type: Failure).
,##[error]The remote provider was unable to process the request.
calvaradocl commented 2 years ago

Same issue from my side. The status of the pipelines are being reported as Healthy.

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

,##[error]The remote provider was unable to process the request. Pool: Azure Pipelines Image: ubuntu-18.04 Started: Just now Duration: 15s

Job preparation parameters 1 queue time variable used

alelfreitas commented 2 years ago

Same here...

waylonmtz commented 2 years ago

we are having this issue too

andrewwiebe commented 2 years ago

Yup same issue here

GuerreiroLeonardo commented 2 years ago

Same here

kummerer94 commented 2 years ago

Same issue.

wesselkranenborg commented 2 years ago

Same here

aphavichitr commented 2 years ago

Same here

jwyglendowski-precisionlender commented 2 years ago

Same here

mvanhulzen commented 2 years ago

Same here, My fix was reverting to ubuntu-16.04. that did work

ldelpozo commented 2 years ago

same here

TejshreeYeole commented 2 years ago

same here

wesselkranenborg commented 2 years ago

Same here, My fix was reverting to ubuntu-16.04. that did work

That's not a fix @mvanhulzen ;-)

MartynasKer commented 2 years ago

same here

warleipereira commented 2 years ago

same here

MattJeanes commented 2 years ago

What Azure DevOps region is everyone in? React to this comment:

You can find this info in organisation settings: image

👍🏻 - United States 👎🏻 - Canada 😄 - Brazil 🎉- Europe 😕 - United Kingdom ❤️ - Asia Pacific 🚀 - Australia 👀 - India

karsegri commented 2 years ago

Same issue over here!

acheraime commented 2 years ago

Same issue here.

maximhazankin commented 2 years ago

Same here

nigreany commented 2 years ago

Same here - East US 2

[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-latest Started: Today at 2:04 PM Duration: 5m 2s

Job preparation parameters

yellowcitytech commented 2 years ago

Someone broke something for sure....

MattJeanes 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

taha-azzabi commented 2 years ago

Same here Europe, and what a chance I had, were planing a huge release on prod tonight

shaunlavallee commented 2 years ago

Same problem here .. :(

ttaylor29 commented 2 years ago

Same here in US - Alabama.

ramdil commented 2 years ago

same problem, we are in US vs2017-win2016

asehgalxom commented 2 years ago

Same problem here, thought I broke something until I saw this thread lol

yuriduque-ciandt commented 2 years ago

mesmo problema aqui

maxxychen commented 2 years ago

same problem, vs2017-win2016, East US

choksz commented 2 years ago

same issue I thought I broke something on my end. tried ubuntu-latest and windows-latest no luck.

jeev20 commented 2 years ago

Yup down here (Norway) as well. Build fails.

digimaun commented 2 years ago

Concur, having the same issue here.

gavinsteinhoff commented 2 years ago

Looks like are all having errors today.

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

[error]The remote provider was unable to process the request.

MarkMastronardi commented 2 years ago

Same here.

gorziza commented 2 years ago

East US Selection_006

elpablete commented 2 years ago

Same here!!!

LR4Discovery commented 2 years ago

Same issue in North Central

LucasFievet commented 2 years ago

Same here :(

acons-TCA commented 2 years ago

Same on East US

chiller-whale commented 2 years ago

Same here :(

NicoleSelig commented 2 years ago

Same here -- East US

saiiii commented 2 years ago

Same all over the world!

jjcaraballo01 commented 2 years ago

Same issues here Central US. Well so much for that deadline we're trying to hit converting all Bamboo and Octopus Deploy plans to YAML pipelines in ADO by eow ;(