Maven Build Failure The 'report' parameter is missing

[bmli...@gmail.com]

We upgraded to SonarQube 6.6.0 and have started to receive an error stating " The 'report' parameter is missing"  when executing the sonar maven plugin.  What parameter is this talking about?  Everything looks to have executed.

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (sonar-analysis) on project elasticsearchplugin: The 'report' parameter is missing

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: The 'report' parameter is missing

        at org.sonarsource.scanner.maven.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:36)

        at org.sonarsource.scanner.maven.bootstrap.ScannerBootstrapper.execute(ScannerBootstrapper.java:81)

        at org.sonarsource.scanner.maven.SonarQubeMojo.execute(SonarQubeMojo.java:122)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

[Julien HENRY]

Hi,

Don't you have a longer stacktrace?

Regards,

Julien

[mstij...@gmail.com]

Having the same issue at the moment. Have you resolved the issue?

[Julien HENRY]

Hi,

I would still need a full log output / stacktrace to better understand the issue.

++

Julien Henry | SonarSource

Developer

https://sonarsource.com

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/07c7vA9Ye0g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/6e36157f-f7f3-4efa-9440-5e8c566c8669%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[bmli...@gmail.com]

We upgraded our sonarqube version from 6.6.0 and the problem went away.

Thanks

[smana...@gmail.com]

Hi, 

I have attached mine in the file. Please let me know. I've been stuck on this report param missing issue for too long. 

https://drive.google.com/open?id=1_oSuGoMMi3-Qp6V28iSMYlAyxUO2Wa33

To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.

[Julien HENRY]

Hi,

Thanks for the logs, it helps to know exactly where the issue happens. Still I don't understand the root cause. I'll try to give you as many details as possible, so that maybe you can see if there is something special on your side.

So the scanner is sending a POST request to http://localhost:9000/api/ce/submit?projectKey=com.tacton.tcsite.wilo.addon:wilo-line-item-management&projectName=Wilo%20Line%20Item%20Management, with a multipart body that is supposed to contains the attached scanner report (ZIP file).

The server is complaining that the attached report is missing in the request body.

I'm not able to reproduce, so it would be interesting if you could investigate on your side, using a network sniffer like wireshark, to see if the request is fine or not (does it contain the "report" parameter?).

For example here is what I see on my side:

++

Julien Henry | SonarSource

Developer

https://sonarsource.com

To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/59b1df6f-ca2f-4819-b919-3a605696a845%40googlegroups.com.

[Syed Muhammad Ali Naqvi]

Thanks, I'll take a look.

[Syed Muhammad Ali Naqvi]

I am running it using 
mvn sonar:sonar -Dsonar.host.url=http://localhost:9000 -Dsonar.login=944da4c39212cf5ed9656f31d84ddf4c96530fb1

command. Is there anything wrong with my command? Actually WireShark or Fiddler isn't showing any request. 
Perhaps it is checking report before sending it to sonar server. 

[Julien HENRY]

Your command looks good. Wireshark should show a lot of requests (the scanner is performing many different WS calls) so I would check your capture configuration. In my screenshot I have only captured the final POST that send the report.

Julien Henry | SonarSource

Developer

https://sonarsource.com

[Syed Muhammad Ali Naqvi]

Should I share my capture information? 

[Julien HENRY]

Yes please, you can send it to me privately.

Julien Henry | SonarSource

Developer

https://sonarsource.com

[Syed Muhammad Ali Naqvi]

If anyone is still facing this issue, please check the logs that are in the sonar directory. My issue was fixed by the help of those logs. Sometime a deadlock is created on the folder and sonar is unable to upload the report due to which report param is missing error occurs. After taking the appropriate action just restart the sonar service. This will definitely sort out the issue. 

And also "Julien" helped a lot in sorting this issue out. 

Regards

On Wed, Feb 21, 2018 at 7:26 PM, Julien HENRY <julien...@sonarsource.com> wrote:

Cool!

Can you please reply to the list with the maximum details (I'm not sure to understand what kind of lock you are talking about, is it a Windows specific feature?). It could help other people.

Thanks

Julien Henry | SonarSource

Developer

https://sonarsource.com

2018-02-21 15:22 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:

Hi Julien, 

Thanks for your time. My issue is fixed now. It was creating a deadlock on the folder. Just saw one issue on the internet and they advised to check the sonar logs. 
And then I came to knew that it has the logs folder and checked the logs, and voilla. It worked. Just restarted the service and removed the lock file. 

Thanks again. 

On Wed, Feb 21, 2018 at 6:44 PM, Syed Muhammad Ali Naqvi <smana...@gmail.com> wrote:

This report is generated in my project target "target\sonar\scanner-report" folder. Not on the server. But why it's not uploading the report, is still a mystery. 

On Wed, Feb 21, 2018 at 6:39 PM, Julien HENRY <julien...@sonarsource.com> wrote:

Wait, how do you get this analysis.log? In the background task UI? If yes then it means the scanner report was correctly received by the server, so I'm even more puzzled.

Regarding Wireshark, I'm targetting the loopback interface, and filtering to only keep packets for port 9000:

Julien Henry | SonarSource

Developer

https://sonarsource.com

2018-02-21 14:30 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:

I am also attaching the file generated by Sonar. Perhaps you can find something in this file that can help me sort out the issue. 

On Wed, Feb 21, 2018 at 6:19 PM, Syed Muhammad Ali Naqvi <smana...@gmail.com> wrote:

I have been trying to do it. How can I see my localhost traffic? Can you please mention the step? Thanks. I am using windows 10

On Wed, Feb 21, 2018 at 6:08 PM, Julien HENRY <julien...@sonarsource.com> wrote:

I'm a bit confused. In your previous logs the server URL was http://localhost:9000 but your capture seems to only contains connections to 192.168.0.xx with SSL. Can you clarify? Have you selected the correct interface (loopback) when doing the capture?

Julien Henry | SonarSource

Developer

https://sonarsource.com

2018-02-21 13:43 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:

Hi Henry, Please find the attached scan. 

I truly appreciate the way you are helping.