# Update loop or failed due to upgrade\_available

**URL:** <https://hub.mender.io/t/update-loop-or-failed-due-to-upgrade-available/7643>\
**Category:** General Discussions\
**Tags:** yocto, mender-client, scarthgap\
**Created:** [March 18, 2025, 4:03pm UTC](https://hub.mender.io/t/update-loop-or-failed-due-to-upgrade-available/7643 "2025-03-18T16:03:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yairbenavraham](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yairbenavraham/32/2451_2.png) [@yairbenavraham](https://hub.mender.io/u/yairbenavraham)\
**Post date:** [March 18, 2025, 4:03pm UTC](https://hub.mender.io/t/update-loop-or-failed-due-to-upgrade-available/7643/1 "2025-03-18T16:03:07Z")

</div>

Hi,

After updating the board (Variscite imx8mp dart) the deployment status changed from ‘_Downloading_’ to ‘_Rebooting_’, the board goes into reboot and boot into the newly updated partition.  
On the demo server side, after the reboot, if the ‘_upgrade\_available_’ environment variable equal ‘1’ then the deployment status changed to ‘_failure_’. On the other hand, if ‘_upgrade\_available_’ equal ‘0’, the deployment status changed back to ‘_Downloading_’ and the whole update process starts over again.  
Yocto scarthgap  
mender 4.0.6  
mender-client 3.5.3

Any idea?

Thanks,  
Yair

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [March 20, 2025, 10:47am UTC](https://hub.mender.io/t/update-loop-or-failed-due-to-upgrade-available/7643/2 "2025-03-20T10:47:58Z")

</div>

Hi @yairbenavraham,

Sorry, I can’t completely follow. So do I understand correctly:

- you are not using the standalone flow in the described situation. The deployment is triggered through a server instance, such as `hosted.mender.io`.
- the reboot occurs automatically, and exactly once
- after that, the board is running the new software, but the deployment on the server is never finished and stuck in rebooting. Is that correct?

One thing that sounds strange is the versions:

1. `mender` 4.0.6 AND
2. `mender-client` 3.5.3  
Do you have both installed on the device? Can you eventually provide the list of installed packages? Two clients running at the same time would definitely have unexpected effects.

The handling of `upgrade_available` and `bootcount` should not require any manual handling. You can check their correct operation using the [integration checklist](https://docs.mender.io/client-installation/integration-checklist)

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![yairbenavraham](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yairbenavraham/32/2451_2.png) [@yairbenavraham](https://hub.mender.io/u/yairbenavraham)\
**Post date:** [March 20, 2025, 11:05am UTC](https://hub.mender.io/t/update-loop-or-failed-due-to-upgrade-available/7643/3 "2025-03-20T11:05:52Z")

</div>

Hi @TheYoctoJester ,

Your understanding is correct: deployment is triggered through a server instance, reboot occurs automatically to the newly updated partition, deployment on the server is never finished: stuck in rebooting but after a while changed to downloading.  
The installed and running mender is Mender 4.0.6.

 ![mender_client_version](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/6/6c23e4150ca3840f1c4db7668ede80f507e0c5ce.png)