After upgrade to Sonar to 10.6 Error: Checksum verification failed for JRE

SonarQube Server / Community Build
23

Indeed, the JRE provisioning feature mentioned does seem to be causing an issue for you. I was hoping to resolve this without skipping provisioning, but it is a valid workaround.

before 10.6 we relied on the user to have installed and configure a valid java version on the host machine (e.g. java 10.7) so if this was indeed working before, it meant that the machine had java installed.

When turning off JRE provisioning you’ll be responsible for configuring your Java instance

Error: Java not found in PATH

Here is some documentation around when JRE provisioning is not being used
https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/scanner-environment/general-requirements/#if-jre-auto-provisioning-is-not-supported

1 Like
24

I think there is potential for this to be an issue with anything the bootstrapper downloads, not just with the JRE provisioning. I have JRE provisioning disabled and have Java set up correctly but the checksum verification failure still occurs, just on a different file…

Error: Checksum verification failed for /home/runner/.sonar/cache/1b76f869ed4c5f9dc822a0736eb5286d020ce75f00b4d80d42305bd0a49809c6/sonarcloud-scanner-engine-11.4.0.221.jar. Expected checksum 1b76f869ed4c5f9dc822a0736eb5286d020ce75f00b4d80d42305bd0a49809c6 but got 53e5a17c59a02e32b3f33231e03bf55417656a3ce52cdd865d8e45acc291ce9b
1 Like
25

I observed the same behavior when there is parallel execution via the npm package sonarqube-scanner@4.2.6 regardless of the jre provisioning feature when the scans use the same value of the sonar.userHome property - see github ci run. A workaround is to scan sequentiell which slows down ci.

Unrelated to this topic but since you are also having a monorepo setup: When the sonar scan adds a new project as part of the first scan, it fails in the ci run of the pull request - it wants a default branch, see github ci run. I wonder why its not defining one or saying what sonar.* property needs to be set. My workaround is to run it locally, which is obviously not github actions and my guess is that because this github actions auto configure pr or branch analysis feature is not active, the sonar scan falls back to branch analysis, which unfortunately sets the default main branch to master- so I need to manually change it after the run via the UI - this feels wrong. Im new to sonar, do you have any advice?

Cheers