Device is not able to provision


I’ve just created a new openBalena instance (see below for details), and tried to add a device to it, however I get the following error on the supervisor of the device:

[event]   Event: Device bootstrap {}
[info]    New device detected. Provisioning...
[event]   Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":"Device weathered-sun is too old to satisfy required version range: &gt;=2.11.0","stack":"ApiError: Device weathered-sun is too old to satisfy required version range: &gt;=2.11.0\n    at Object.<anonymous> (/usr/src/app/dist/app.js:10:452890)\n    at (<anonymous>)\n    at fulfilled (/usr/src/app/dist/app.js:10:1915792)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)"}}

Fresh openBalena instance and downloaded the newest version of BalenaOS from
Configured the image as follow:

balena os configure <path-to-img> --app <app-name>

openBalena details:
API version: 0.119.5
DB version: 4.1.0
Registry version: 2.16.0
S3 version: 2.9.9
VPN version: 9.17.4

Device that I’m trying to provision:
Raspberry Pi 4
OS: Version 2.80.3+rev1 (dev)
Supervisor: v2.17.0

Looks like something is wrong with checking the version of the OS or something.

Thanks in advance!

That’s odd! Thank you for reporting @bversluijs i will ping the team internally to see how we can solve this. Did you create an issue?

Hi Marc,

No I didn’t create an issue, because I don’t really know if it’s the openBalena API that’s causing the issue or the supervisor.

I can however create an issue in the open-balena repo as a more “general” issue?

Thanks Marc. Yes - please go ahead and create this as a “general” issue. Do add the above and possibly any other log excerpt if possible. Someone from our team can update as and when we find more info on this.

Hi, we are still investigating this problem. For the mean time, we have created this Github issue to track it: API returns "Device is too old to satisfy required version range" · Issue #696 · balena-io/open-balena-api · GitHub

1 Like

Let me know if there’s anything I can do to help, like creating a new openBalena cluster with a different API image for example!

It’s the only thing at the moment that’s stopping me from releasing a new openBalena Kubernetes chart :slight_smile:

Hi @bversluijs,

I see that the issue has been closed because of your PR. Thanks for your help! This will definitely be useful to other users of openbalena!

Please also don’t hesitate to share your experience of deploying openBalena with Kubernetes. I’m sure that will be appreciated.


1 Like

Hi @pipex,

Thanks for your reaction in this thread. Completely forgot that I’ve created a thread about in on the forums, but the issue has indeed been resolved by upgrading the API service, which is merged into te master branch now.

And I’ll definitely share my experience of deploying on Kubernetes!


1 Like

That’s great! Looking forward to that :slight_smile:

1 Like