We are investigating your issue and trying to understand why your pipeline started failing. It is related to the last release, but we think there may be something specific to your setup that is, somehow, not working well with this update.
We would need more information to investigate. Could you please tell me if you are using SonarQube behind a reverse proxy?
Also, we would need the full execution log for a failing CI run, including debug logs (You have to check “Enable system diagnostics”)
Adding my voice to this issue. With the latest update to 5.16.0 that automatically happened 3 hours ago, all our build pipelines started failing with “##[error][SQ] API GET ‘/api/server/version’ failed, error is Request failed with status code 500”
This is with SonarQube 9.9.1 Community Edition behind a reverse proxy.
I’ll follow up with detailed logs.
Edit: Detailed logs as follows:
##[debug]Evaluating: succeeded()
##[debug]Evaluating succeeded:
##[debug]=> True
##[debug]Result: True
Starting: Prepare analysis on SonarQube
==============================================================================
Task : Prepare Analysis Configuration
Description : Prepare SonarQube analysis configuration
Version : 5.16.0
Author : sonarsource
Help : Version: 5.16.0. [More Information](http://redirect.sonarsource.com/doc/install-configure-scanner-tfs-ts.html)
==============================================================================
##[debug]Using node path: ***\Agent-01\externals\node10\bin\node.exe
##[debug]agent.TempDirectory=***\Agent-01\build\_temp
##[debug]loading inputs and endpoints
##[debug]loading ENDPOINT_AUTH_***
##[debug]loading ENDPOINT_AUTH_PARAMETER_***_USERNAME
##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
##[debug]loading ENDPOINT_AUTH_SCHEME_***
##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
##[debug]loading INPUT_CLIPROJECTVERSION
##[debug]loading INPUT_CLISOURCES
##[debug]loading INPUT_CONFIGFILE
##[debug]loading INPUT_CONFIGMODE
##[debug]loading INPUT_EXTRAPROPERTIES
##[debug]loading INPUT_PROJECTKEY
##[debug]loading INPUT_PROJECTNAME
##[debug]loading INPUT_PROJECTVERSION
##[debug]loading INPUT_SCANNERMODE
##[debug]loading INPUT_SONARQUBE
##[debug]loaded 16
##[debug]Agent.ProxyUrl=***
##[debug]Agent.ProxyUsername=undefined
##[debug]Agent.ProxyPassword=undefined
##[debug]Agent.ProxyBypassList=["localhost","***"]
##[debug]expose agent proxy configuration.
##[debug]Agent.CAInfo=undefined
##[debug]Agent.ClientCert=undefined
##[debug]Agent.SkipCertValidation=undefined
##[debug]SonarQube=***
##[debug]***=https://sonarqube.***/sonar/
##[debug]*** auth param apitoken = undefined
##[debug]*** auth param username = ***
##[debug]*** auth param password = undefined
##[debug]organization=undefined
##[debug]scannerMode=MSBuild
##[debug]projectKey=project
##[debug]projectName=project
##[debug]projectVersion=2.0
##[debug]organization=undefined
##[debug][SQ] API GET: '/api/server/version' with query "undefined"
##[debug][SQ] API GET '/api/server/version' failed, status code was: 500
##[debug]task result: Failed
##[error][SQ] API GET '/api/server/version' failed, error is Request failed with status code 500
##[debug]Processed: ##vso[task.issue type=error;][SQ] API GET '/api/server/version' failed, error is Request failed with status code 500
##[debug]Processed: ##vso[task.complete result=Failed;][SQ] API GET '/api/server/version' failed, error is Request failed with status code 500
Finishing: Prepare analysis on SonarQube```
GET requests via the browser to /api/server/version result in the current version number as a response:
9.9.1.69595
Hi,
I was now able to take a closer look at the problem.
Our SonarQube is behind a reverse proxy.
The problem only occurs with on-premise build agents that are behind a proxy (without authentication). It works for agents hosted in Azure which don’t use a proxy.
According to the logs, Chris’s setup looks the same.
@cba@andreasfischer we’ve released a patch version of SQ extension 5.17.1 which we hope resolves the issue. Could you let us know if the change works well on your side?
Thanks for your support. For us it is still failing with the same error. But now we have more log output about the reason.
I add here the relevant part of the log:
2023-10-18T11:02:19.0539048Z ##[debug][SQ] API GET: '/api/server/version' with query "undefined"
2023-10-18T11:02:19.1620008Z ##[debug][SQ] API GET '/api/server/version' failed, status code was: 400
2023-10-18T11:02:19.1629577Z ##[debug]API GET error response data: "<HTML>***</HTML>\r\n\t"
2023-10-18T11:02:19.1636288Z ##[debug]API GET error object: {"message":"Request failed with status code 400","name":"AxiosError","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"transformRequest":[null],"transformResponse":[null],"timeout":60000,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","host":"***.com"},"url":"/api/server/version","method":"get","baseURL":"https://***.com/sonarqube","auth":{"username":***}},"code":"ERR_BAD_REQUEST","status":400}
2023-10-18T11:02:19.1637484Z ##[debug]task result: Failed
2023-10-18T11:02:19.1677587Z ##[error][SQ] API GET '/api/server/version' failed, error is Request failed with status code 400
2023-10-18T11:02:19.1685997Z ##[debug]Processed: ##vso[task.issue type=error;][SQ] API GET '/api/server/version' failed, error is Request failed with status code 400
2023-10-18T11:02:19.1687360Z ##[debug]Processed: ##vso[task.complete result=Failed;][SQ] API GET '/api/server/version' failed, error is Request failed with status code 400
From the error response data I extracted the following message:
Request Error
This could be caused by a misconfiguration, or possibly a malformed request.
Sorry, your request could not be processed. Request could not be handled
This message is from the corporate proxy. So it looks like the request does not reach SonarQube.
The issue is now solved with 15.7.2. Thanks for your support!
I raised a ticket at our IT support to check why the request couldn’t pass the corporate proxy. In case I get some insights why this happened I will add the information here.