ERROR cannot deliver device serial request: unexpected status 400

Ara Pulido ara.pulido at canonical.com
Thu Feb 2 09:01:49 UTC 2017


On Thu, Feb 2, 2017 at 7:55 AM, Bruno Morelli <b.morelli at evidence.eu.com>
wrote:

> I've created kernel and gadget snaps for my new board.
> I successfully deployed the image created by ubuntu-image into the emmc of
> my board.
>
> I can complete the device configuration (console-conf terminates with the
> message "Congratulations! This device is now registered to" ...).
>
> Logging into my device and typing:
>
> snap changes
>
> I obtain the following output:
> ID   Status  Spawn                 Ready                 Summary
> 1    Done    2017-01-30T09:02:08Z  2017-01-30T09:04:08Z  Initialize system
> state
> 2    Doing   2017-01-30T09:02:18Z  -                     Initialize device
>
> The system change with ID 2 ("Initialize device") seems to be in progress.
> More in detail with the command:
>
> snap change 2
>
> I obtain:
>
> Status  Spawn                 Ready                 Summary
> Done    2017-01-30T09:02:18Z  2017-01-30T09:04:08Z  Generate device key
> Doing   2017-01-30T09:02:18Z  -                     Request device serial
> ......................................................................
> Request device serial
> 2017-01-30T09:24:06Z ERROR cannot deliver device serial request:
> unexpected status 400
> 2017-01-30T09:25:09Z ERROR cannot deliver device serial request:
> unexpected status 400
> 2017-01-30T09:26:12Z ERROR cannot deliver device serial request:
> unexpected status 400
> 2017-01-30T09:27:15Z ERROR cannot deliver device serial request:
> unexpected status 400
> [...]
>
>
> Am I missing something in my gadget snap implementation?
> Is only an Ubuntu server side problem?
>
>
Your device is trying to get a serial assertion from the Ubuntu servers,
but your model is not one of the Ubuntu official ones, so that is not
possible.

If you want your device to get a proper serial assertion (for example, if
you want to create a production ready device), you will need to deploy your
own service to issue those signed serial assertions and add a
prepare-device hook to your gadget snap.

If you are not planning to create a production device, you can safely
ignore those errors.

But I agree that the error from the store should give more information.

Thanks,
Ara.

[1] https://docs.ubuntu.com/core/en/guides/build-device/config-hooks


> Regards,
> Bruno
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170202/0f16d443/attachment.html>


More information about the Snapcraft mailing list