SonarQube Code Analysis Expected — Waiting for status to be reported

[Kostiantyn_Koloskov]

Hello

I use:
SonarQube → 9.9.0 in docker, Postgresql → 14.6, CI → Jenkins.
I use DevOps Platform Integrations with GitHub app.
SonarQube returns validation status and no problems.

Problem:
After upgrading to sonarqube version 10.0.0, they stop sending check status to GitHub and hangs on SonarQube Code Analysis Expected - Waiting for status to be reported.
In sonarqube itself, all checks passed successfully.
The problem applies to all our projects starting from the new version, when returning to the old version, everything works successfully.

Log in Sonar:

2023.06.01 04:05:55 INFO  ce[][o.s.c.t.CeWorkerImpl] Execute task | project= MyProjectName | type=REPORT | pullRequest=954 | id=AYh1IirZNw3Lo2sOAeTP | submitter=admin
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Extract report | status=SUCCESS | time=389ms
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist scanner context | status=SUCCESS | time=9ms
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Propagate analysis warnings from scanner report | status=SUCCESS | time=4ms
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Generate analysis UUID | status=SUCCESS | time=0ms
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load analysis metadata | status=SUCCESS | time=15ms
2023.06.01 04:05:55 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Initialize | status=SUCCESS | time=13ms
2023.06.01 04:05:56 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Build tree of components | components=1 | status=SUCCESS | time=261ms
2023.06.01 04:05:56 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Validate project | status=SUCCESS | time=3ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load quality profiles | status=SUCCESS | time=1600ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load file hashes and statuses | status=SUCCESS | time=7ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load Quality gate | status=SUCCESS | time=5ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load new code period | status=SUCCESS | time=0ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Detect file moves | status=SUCCESS | time=0ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Detect file moves in Pull Request scope | reportFiles=0 | status=SUCCESS | time=0ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load duplications | duplications=0 | status=SUCCESS | time=42ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute cross project duplications | status=SUCCESS | time=0ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute size measures | status=SUCCESS | time=0ms
2023.06.01 04:05:57 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute new coverage | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute coverage measures | status=SUCCESS | time=238ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute comment measures | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute duplication measures | status=SUCCESS | time=21ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute size measures on new code | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute language distribution | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute test measures | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute complexity measures | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Load measure computers | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute Quality Profile status | status=SUCCESS | time=5ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Execute component visitors | status=SUCCESS | time=45ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Checks executed after computation of measures | status=SUCCESS | time=3ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute Quality Gate measures | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute Quality profile measures | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Generate Quality profile events | status=SUCCESS | time=2ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Generate Quality gate events | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Check upgrade possibility for not analyzed code files. | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist scanner analysis cache | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist components | status=SUCCESS | time=6ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist analysis | status=SUCCESS | time=3ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist analysis properties | status=SUCCESS | time=4ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist measures | inserts=41 | status=SUCCESS | time=10ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist live measures | insertsOrUpdates=62 | status=SUCCESS | time=18ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist duplication data | insertsOrUpdates=0 | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist new ad hoc Rules | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist issues | cacheSize=0 bytes | inserts=0 | updates=0 | merged=0 | status=SUCCESS | time=1ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Delete issue changes | changes=0 | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist project links | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist events | status=SUCCESS | time=4ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist sources | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Persist cross project duplications | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Enable analysis | status=SUCCESS | time=3ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Update last usage date of quality profiles | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Purge db | status=SUCCESS | time=36ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Index analysis | status=SUCCESS | time=15ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Update need issue sync for branch | status=SUCCESS | time=2ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Compute total Project ncloc | status=SUCCESS | time=5ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Publishing taint vulnerabilities events | status=SUCCESS | time=2ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Send issue notifications | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Publish task results | status=SUCCESS | time=0ms
2023.06.01 04:05:58 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.s.ComputationStepExecutor] Trigger refresh of Portfolios and Applications | status=SUCCESS | time=0ms
2023.06.01 04:06:08 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Webhooks | globalWebhooks=1 | projectWebhooks=0 | status=SUCCESS | time=10032ms
2023.06.01 04:06:08 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Pull Request decoration | status=SUCCESS | time=5ms
2023.06.01 04:06:08 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Report branch Quality Gate status to devops platforms | status=SUCCESS | time=0ms
2023.06.01 04:06:08 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.CeWorkerImpl] Executed task | project=MyProjectName | type=REPORT | pullRequest=954 | id=AYh1IirZNw3Lo2sOAeTP | submitter=admin | status=SUCCESS | time=13237ms

Screenshot in GitHub:

[Colin]

Hey there.

Take a look at this thread here:

SonarQube 10.0 not reporting quality gate status and PR decoration in Azure DevOps

Hey all. In SonarQube v10.0, we removed some deprecated analysis parameters which, among other things, automatically fed the ALM Integration information when in an Azure Pipelines context (using the Extension for Azure Devops) This was old behavior, kept for compatibility reasons, and we’ve encouraged users to set the ALM integration configuration in their Project Settings for some time now. Right now, there’s no method of automatically populating this data from information available to the s…

[Kostiantyn_Koloskov]

Thanks for the link

As far as I can see this post is related to Azure DevOps
We not use Azure DevOps we use GitHub DevOps Platform Integrations

I asked our developers what properties we use:

properties {
        property "sonar.projectName", rootProject.name
        property "sonar.projectKey", "${project.group}:${rootProject.name}"
        property "sonar.moduleKey", "${project.group}:${rootProject.name}"

        property "sonar.java.pmd.reportPaths", "./build/reports/pmd/main.xml"
        property "sonar.java.checkstyle.reportPaths", "./build/reports/checkstyle/main.xml"
        property "sonar.coverage.jacoco.xmlReportPaths", "./build/reports/jacoco/test/jacocoTestReport.xml"

        property "sonar.issue.ignore.multicriteria", "e1"
        property "sonar.issue.ignore.multicriteria.e1.ruleKey", "java:S120"
        property "sonar.issue.ignore.multicriteria.e1.resourceKey", "**/Actors/**"
    }

He said that’s all
Are there any other options for what it could be?

[Kostiantyn_Koloskov]

Is there new information?

[Colin]

Hey there.

I must have gotten my wires crossed – not sure where Azure DevOps came from!

• Can you check to make sure the repository details are correct under your Project Settings > DevOps Platform Integrations
• If necessary, you can increase the log level (global Administration > System > Log Level) to understand what exactly the Compute Engine is doing during this step (if it’s making a request at all).

@Kostiantyn_Koloskov

2023.06.01 04:06:08 INFO  ce[AYh1IirZNw3Lo2sOAeTP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Pull Request decoration | status=SUCCESS | time=5ms

[Kostiantyn_Koloskov]

Thanks a lot Colin
I found a solution by increasing the logs

In my case, it was necessary to set up DevOps integration at the project level and remove unnecessary decorations:
sonar.pullrequest.provider
sonar.pullrequest.github.repository