dkms info is malformed in submission.json

[Sheila Miguez]

This was found by bladernr when reporting a hexr/c3 bug, lp:1736268:

"First, I have two tarballs. One came from hyperscale team who did testing using the dev PPA versions of checkbox-ng. The other is testing I did locally also using the current dev PPA versions of checkbox-ng. One I was able to submit using checkbox-cli, the other gives me a 500 error."

The submissions that were rejected by c3 had invalid entries for dkms_info:

"dkms_info": ,

I've attached one of the submissions that failed.

[Jeff Lane  (bladernr)]

This blocks successful submissions both internally and externally, hence the severity...

[Sylvain Pineau (sylvain-pineau)]

        {
            "id": "miscellanea/submission-resources",
            "name": "Check that data for a complete result are present",
            "certification_status": "unspecified",
            "category": "com.canonical.plainbox::miscellanea",
            "status": "skip",
            "comments": "job cannot be started: required dependency 'com.canonical.certification::dkms_info_json' has failed",
            "io_log": "",
            "type": "test",
            "project": "certification"
        },

We would need someone to run the following command on the system which failed to submit:

dkms_info --format json | plainbox dev parse dkms-info | jq --indent 4 '.dkms_info'

Since it's an attachment job, unfortunately the tarball does not contain the corresponding files that could help knowing what happened.

@Jeff, do you think you can get access to this system?

[Jeff Lane  (bladernr)]

Oh geez... Sylvain, if you ever have questions for me on bugs and I fail to answer in a reasonable time, please ping me directly. Unfortunately, I get so much mail from launchpad that these things sometimes get buried or filtered out of sight :(

I'm sorry I missed your request completely. But thanks for solving it despite that!

[Sylvain Pineau (sylvain-pineau)]

no problem Jeff, I've been looking at this bug many time since January and I've finally found why...today. the system was just missing dkms (the package) and the job does not really depend on it so I've removed its req.