This incident has been resolved. Our DNS provider has resolved an issue on its side and our monitoring shows that normal traffic has resumed. We apologize for the inconvenience.
[11:02 a.m. EST] Current status: We have expanded our DNS name service level and are seeing positive indications. Please respond here with your CI provider and region, if available, if you are still experiencing failures
Root causes: We are continuing to investigate root causes, but our DNS provider has just reported a major incident.
Symptoms: DNS for some CI providers was failing to resolve SonarCloud.io, which caused analysis to fail.
Â
Again, please respond here if you’re still experiencing problems. It will be helpful to know your CI provider and region.
[7:51 a.m. EST]
Hi all,
SonarCloud.io cannot be resolved by some of our customers. As a consequence, static analysis cannot be performed. Our engineering teams are currently troubleshooting this issue with top priority. Preliminary investigations are pointing to a DNS issue.
I have consolidated reports of this outage here in this thread so there is a single, central place to go for updates.
As we know more, we’ll add it here. Please use the bell () icon to subscribe to updates on this thread. You can also watch https://sonarcloud.statuspage.io/
Our CI is down with this message:
ERROR: SonarCloud server [https://sonarcloud.io] can not be reached
Sonar cloud status page is green.
The website seems to work fine.
Is there an issue?
Witnessing the same thing. It started yesterday in sync with the AZURE networking outage I believe. Then it came back up, but I guess it’s back to being “down” this morning.
Not sure why the status page is not reporting anything.
We are witnessing issues when running sonar scans as part of our CI pipelines.
The scanner fails with the following error:
10:00:23.131 DEBUG: Extract sonar-scanner-api-batch in temp...
10:00:23.136 DEBUG: Get bootstrap index...
10:00:23.136 DEBUG: Download: https://sonarcloud.io/batch/index
10:00:29.196 ERROR: SonarCloud server [https://sonarcloud.io] can not be reached
10:00:29.197 INFO: ------------------------------------------------------------------------
10:00:29.197 INFO: EXECUTION FAILURE
10:00:29.197 INFO: ------------------------------------------------------------------------
10:00:29.198 INFO: Total time: 6.627s
10:00:29.219 INFO: Final Memory: 8M/887M
10:00:29.219 INFO: ------------------------------------------------------------------------
10:00:29.219 ERROR: Error during SonarScanner execution
org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarScanner analysis
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:85)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:74)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:70)
at org.sonarsource.scanner.api.EmbeddedScanner.doStart(EmbeddedScanner.java:185)
at org.sonarsource.scanner.api.EmbeddedScanner.start(EmbeddedScanner.java:123)
at org.sonarsource.scanner.cli.Main.execute(Main.java:74)
at org.sonarsource.scanner.cli.Main.main(Main.java:62)
Caused by: java.lang.IllegalStateException: Fail to get bootstrap index from server
at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:42)
at org.sonarsource.scanner.api.internal.JarDownloader.getScannerEngineFiles(JarDownloader.java:58)
at org.sonarsource.scanner.api.internal.JarDownloader.download(JarDownloader.java:53)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:76)
... 7 more
Caused by: java.net.UnknownHostException: sonarcloud.io: Temporary failure in name resolution
at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source)
at java.base/java.net.InetAddress.getAddressesFromNameService(Unknown Source)
at java.base/java.net.InetAddress$NameServiceAddresses.get(Unknown Source)
at java.base/java.net.InetAddress.getAllByName0(Unknown Source)
at java.base/java.net.InetAddress.getAllByName(Unknown Source)
at java.base/java.net.InetAddress.getAllByName(Unknown Source)
at org.sonarsource.scanner.api.internal.shaded.okhttp.Dns.lambda$static$0(Dns.java:39)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.java:171)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.nextProxy(RouteSelector.java:135)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.RouteSelector.next(RouteSelector.java:84)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.java:187)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.java:108)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ExchangeFinder.find(ExchangeFinder.java:88)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.Transmitter.newExchange(Transmitter.java:169)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:41)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:94)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:88)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:142)
at org.sonarsource.scanner.api.internal.shaded.okhttp.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:117)
at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.getResponseWithInterceptorChain(RealCall.java:221)
at org.sonarsource.scanner.api.internal.shaded.okhttp.RealCall.execute(RealCall.java:81)
at org.sonarsource.scanner.api.internal.ServerConnection.callUrl(ServerConnection.java:115)
at org.sonarsource.scanner.api.internal.ServerConnection.downloadString(ServerConnection.java:99)
at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:39)
The status page is not reporting any incidents and it seems that other people in the communicty are facing the same issues.
Any idea of what’s happening or what was recently upgraded ?
We have the same issues in our gitlab pipelines. We let the gitlab support staff check our pipelines and they verified a DNS configuration issue on sonarcloud’s side.
However, it seems that when we use different gitlab runners running in AWS they don’t seem to have troubles connecting to sonarcloud.io while the google cloud based gitlab shared runners do have problems.
Did the DNS configuration for sonarcloud.io change recently?
I am able to resolve sonarcloud.io on my laptop, I can access the UI and I can ping the API. However, the dns resolution fails in our Kubernetes clusters hosted in Azure.
I believe not only Azure infrastructure is affected, as people are facing the same issue on different cloud providers. So I can only assume this is from sonarcloud’s side.
the same issue we are facing on GitHub Actions Managed Runners. It is not resolving
ERROR: SonarCloud server [https://sonarcloud.io] can not be reached
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 5.347s
INFO: Final Memory: 3M/17M
ERROR: Error during SonarScanner execution
INFO: ------------------------------------------------------------------------
org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarScanner analysis
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:85)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:74)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:70)
at org.sonarsource.scanner.api.EmbeddedScanner.doStart(EmbeddedScanner.java:185)
at org.sonarsource.scanner.api.EmbeddedScanner.start(EmbeddedScanner.java:123)
at org.sonarsource.scanner.cli.Main.execute(Main.java:73)
at org.sonarsource.scanner.cli.Main.main(Main.java:61)
Caused by: java.lang.IllegalStateException: Fail to get bootstrap index from server
at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(BootstrapIndexDownloader.java:42)
at org.sonarsource.scanner.api.internal.JarDownloader.getScannerEngineFiles(JarDownloader.java:58)
at org.sonarsource.scanner.api.internal.JarDownloader.download(JarDownloader.java:53)
at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:76)
... 7 more
Thanks for your reports of this issue. They helped us spot the problem and begin to understand the scope. I’ve consolidated all the reports in this new thread I created so there’s one place to go for updates.
I’ve updated the inital post with this, but I’m also adding it as a reply so notifications are sent:
Current status: We have expanded our DNS name service level and are seeing positive indications. Please respond here with your CI provider and region, if available, if you are still experiencing failures
Root causes: We are continuing to investigate root causes, but our DNS provider has just reported a major incident.
Symptoms: DNS for some CI providers was failing to resolve SonarCloud.io, which caused analysis to fail.
Â
Again, please respond here if you’re still experiencing problems. It will be helpful to know your CI provider and region.
This incident has been resolved. Our DNS provider has resolved an issue on its side and our monitoring shows that normal traffic has resumed. We apologize for the inconvenience.