Could not upload data to HEXR when submitting result via checkbox-gui

Hello! It's a known bug; the "share with hexr" button doesn't set the required header when uploading the submission. I need to look at how the GUI communicates with the backend and ensure the request to share is properly taken into account. All the backend code knows how to handle this, it's just that bridge between the GUI having the check mark and the backend actually processing it.

A workaround in the meanwhile is to use the "share with hexr" button in the submission. For instance, https://certification.canonical.com/hardware/201405-15033/submission/99614/ shows a "share with hexr" button next to "link to existing certificate" which should have the same functionality.

If you don't see this "share with hexr" it may be because your user permissions don't give you this option. "only those who can certify, and modify machinereports can share/unshare" and I'm guessing you can't.

I'll ask around if it's possible to give you this permission (though it may take a couple of days). I'll also get to work on fixing the bug itself (which may also take a couple of days).

In the meanwhile, if you want a submission shared with hexr, please e-mail me the submission URL and I'll share it with hexr for you. Once I do, you should get the "view in hexr" control.

This is probably not a -providers bug. ce-qa-concern perhaps?

On Fri, Aug 15, 2014 at 4:28 PM, Roxanne Fan <email address hidden> wrote:
> ** Tags added: ce-qa-providers
>
> --
> You received this bug notification because you are a member of Checkbox
> Bug Wranglers, which is subscribed to Checkbox.
> https://bugs.launchpad.net/bugs/1357338
>
> Title:
> Could not upload data to HEXR when submitting result via checkbox-gui
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/checkbox/+bug/1357338/+subscriptions

Hello!

Thank you all for the feedback and help!
So far there are 2 ways to submit results with uploading data to hexr:
1. via checkbox-gui directly
2. via checbkox-certification-tools :
   $ checkbox-certification-submit --hexr --hwid <Hardware SecureID> <path to submission.xml>

The data can be uploaded to hexr successfully via #2(checkbox-certification-tools) only.
We have to submit results/upload data maunally after testing complete, I think it would be great and much more effieient to have the function back to checkbox-gui. :-)

While triaging this I noticed that the GUI and dbus are propagating the tick mark's setting properly; the problem is that the certification transport (part of the plainbox library) wasn't actually translating that option into the HTTP header required for hexr to slurp the submission. Fixing this now...