##[error] Failed to request and parse 'https://sonarcloud.io/api/server/version': Resource temporarily unavailable

SonarQube Cloud
1

On Saturday, we observed unusual error on azure builds regarding the Sonarcloud resources unavailable.

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    Sonarcloud

  • error observed (wrap logs/code around triple quote ``` for proper formatting)

SonarScanner for MSBuild 4.7.1
Using the .NET Core version of the Scanner for MSBuild
Pre-processing started.
Preparing working directories...
21:35:50.217  Updating build integration targets...
21:35:50.421  Fetching analysis configuration settings...
##[error]21:36:05.841  Failed to request and parse 'https://sonarcloud.io/api/server/version': Resource temporarily unavailable Resource temporarily unavailable
21:36:05.841  Failed to request and parse 'https://sonarcloud.io/api/server/version': Resource temporarily unavailable Resource temporarily unavailable
##[error]Unhandled Exception:

##[error]System.Net.WebException: Resource temporarily unavailable Resource temporarily unavailable ---> System.Net.Http.HttpRequestException: Resource temporarily unavailable ---> System.Net.Sockets.SocketException: Resource temporarily unavailable
   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

image
image1391×229 17.1 KB

  • steps to reproduce
    Observed the error on 11/16/2019, 3:05:29 AM

  • potential workaround
    Looks like the sonarcloud URL was not accessible.

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

2

Hi,

There has been another topic on that subject (Read here) It appears that the issue was coming from few geographical regions on Azure, we were not able to reproduce it on our side, and it seems to be mitigated at the moment.

Please let us know with more details if you still encounter the issue.

Thank you.

Mickaël

3

Hi Mickael,

I have been facing this error since last week.
It was working fine a few days ago.

MicrosoftTeams-image (3)
MicrosoftTeams-image (3)824×460 19.1 KB

4

Hi @Kiran_Pansare

Please open a new topic for next time as this one is quite old and can get pretty far in our history.

Those issues are mostly transient, so I would expect that this is working fine now. Otherwise let us know.

Thank you.