We recently started using Mender 1.7 to deploy updates to a fleet of devices. Update process is going well but we are facing two issues related to deployment and we were wondering if there are “good practices” on how to handle those cases.
The first issue is how to handle preauthorized device going online. We released an important update and communicated about it, now some users are unpacking the device and expect the update to start right away. However if we created the deployment before they started using the device, they won’t receive it until next deployment, and in the meantime are likely to contact customer support to ask why they cannot update.
We were thinking about periodically querying the server to watch for newly added devices and creating a deployment, but this seems quite unpractical and not really the “good” way to use deployments. Are there any other solutions?
The second issue is how to handle a device that encountered an error during update deployment (for instance if the user restarted the device while downloading artifact). The point is similar to the previous one: if the deployment failed, the user thinks that the update will restart right away, but there is no longer a pending deployment for this device.
So same question, do we have to monitor externally failures via the APIs and relaunch automatically a deployment for those devices, or is there a better approach to this?