Hello @arajan,
I had a quick look at the coverage.xml file you shared and I can see this:
<sources>
<source>/home/cpv/workspace/cpv-python-local-build/services</source>
</sources>
By any chance, do you see something similar to the following lines in the logs of the Sonar Scanner?
WARN: Invalid directory path in 'source' element: /home/cpv/workspace/cpv-python-local-build/services
ERROR: Cannot resolve the file path '{filename}' of the coverage report, the file does not exist in all <source>.
ERROR: Cannot resolve {X} file paths, ignoring coverage measures for those files
If that’s the case,I believe that the issue lies with the fact that SonarQube can’t resolve the file paths mentioned in the coverage report. I suspect it is due to this part /home/cpv/workspace/cpv-python-local-build/ which seems unexpected given your properties. You’d probably have to correct the paths somehow.
See this post which describe a similar problem: Code coverage doesn't work with GitHub action
Hope that helps,
Guillaume