I’m also seeing this in a number of pipelines we run across our teams. It’s always in the SonarQubeAnalyze@4 task. I believe the “No message found for this issue” string is actually generated by Azure DevOps when the task.logissue logging command doesn’t have a message passed to it. The syntax for it is described here. Posting error syntax here for clarity:
echo "##vso[task.logissue type=error]My message here"
My bet is that the Sonar scanner VSTS task isn’t adding a message when it calls task.logissue somewhere. Searching the GitHub repo, this is the only place where I can see them emitting an error. If I had to take a guess, based on the surrounding code, their tool.on callback is getting an empty string or just a string with whitespace from the standard error stream. After they trim it, the value is an empty string that they pass to the task.logissue command, thus generating the Azure DevOps build output seen in the original post.