Closed somiya9868 closed 3 years ago
Same West Europe
Same in Brazil with Ubuntu 16
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
We are also having the same issue. We are in South Central US. We are using macOs-10.14
same issue in central us
Same here 😕
same here :(
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
the same here:
,##[error]The remote provider was unable to process the request. Pool: Azure Pipelines Image: Ubuntu16
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.
samesies
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
Same here, Dev team blocked from builds :(
Having the issue as well
Same thing here. Region: Brazil South.
same in Australia East since more than half an hour
yep, same for us, East Canada ubuntu-latest no problems showing here - https://status.dev.azure.com/
Same. Region: East Asia Image: ubuntu-latest
Same problem here. Region: Brazil South.
yep, same for us, East Canada no problems showing here - https://status.dev.azure.com/
Unbelievable!!!
Same problem here "The remote provider was unable to process the request."
Same here
Seeing the same problem across multiple different orgs
same here, Brazil
Same issue. Region: Canada Central, vmImage: Windows-Latest
Same here -> West Europe
We are also experiencing this issue in a Build pipeline.
East US 2 Visual Studio version: latest
There are other issues that were just created also:
The problem is that there is not the place to report service availability issues:
But there is no link to the Service Availability Issue form
Same here, Brazil
Same issue.
same issue here
Same issue in western Canada
Same issue here from U.S.
same issue using a hosted agent in eastern us
Looks like they are finally looking into it.
Same issue
same issue in Brazil.
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
My fellow developers, maybe you are all trying to figure why I have called you here...
+1 Brazil
same issue.
Same issue in Eastern US
They've updated the status page now https://status.dev.azure.com
Fellow developer, what's your favorite programming joke?
Mine: Why Java developers have glasses? Because they can't see sharp. Ba dum tss..
Fellow developer, what's your favorite programming joke?
Mine: Why Java developers have glasses? Because they can't see sharp. Ba dum tss..
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 :)
We are also experiencing this issue in a Build pipeline.
East US 2 Visual Studio version: latest
This is resolved on my end.
It started working for me
Description
The azure pipeline is failing with error
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.