Hello,
I’ve noticed that, when trying to re-deploy an artifact already installed to a device, having the “Force Update” option on (in the “advanced settings” of a deployment, in the Web UI) doesn’t do anything: the deployment is still skipped because the artifact is already installed.
For the context, I’m testing an Update Module that remotely reboots my device. For this Module to be useful, I need to be able to re-apply this Module as many times as I need!
(my device is running Mender Client 3.1.0)
Hi @gsimon2000,
Thanks for reaching out! The forced updates are not available until client version 3.5, see this changelog Mender Client | Mender documentation and ticket Jira.
Guess you saw it as inspiration, there also is a reboot update module example: mender-update-modules/reboot at master · mendersoftware/mender-update-modules · GitHub.
What you can do without updating the client is using a dirty Update Module, see the example at mender-update-modules/dirty at master · mendersoftware/mender-update-modules · GitHub. By putting a reboot in there the device will reboot and mark the update as failed. A failed update is not marked as installed, so you can repeat as many times as you want.
Greetz,
Josef
Hello,
Thank you very much for your reply! Switching to Mender Client 3.5.0 fixed the problem, the module works like a charm now.
Best,
Guillaume
1 Like