Azure Device Update result code 606 still results in device rebooting immediately

Question

Hello,

I have been using ADU for many years now, but a feature is still not working. As our devices are working in production, they are not allowed to reboot during working hours, they must stay on, so when an update occurs, the device must wait for the night to reboot. I found result code 606 of swupdate handler file that is supposed to mean "Success but deferred reboot" following this documentation, but the devices are still rebooting immediately after updating.

Answer 1

Posting the findings from the Product team to help community members that might stumble on this issue.

The DU Agent supports multi-step updates, where each step can be considered a mini-update for a specific part of the device. Think of it like this:

Step 1: Update the bootloader

Step 2: Update the OS image

Step 3: Perform additional tasks

Each step may require a reboot to occur immediately before moving on to the next step. However, in some update scenario, some step may require a reboot that doesn't need to happen immediately after that step is completed. In this case, deferring the reboot (XYZ_reboot_required) means postponing the reboot process until the very last step is successfully completed.

To address this use case, a work around can be to add a step that waits till night to complete so that the reboot gets triggered after it is done.

Answer 2

Hello @LALANNE Jeremie - CELLENZA ,

welcome to this moderated Azure community forum.

Azure Device Update is part of the Azure IoT Hub functionality.

The Azure IoT Hub gets support for security updates and bug fixes.

Since this behavior seems different from the expected (and documented) behavior, I recommend created a support ticket.

---

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.