Yesterday afternoon we pushed an update to our app. Most of the devices downloaded the update quickly, however one of them is having issues. It has been stuck on the updating step for almost 24 hours. It will download part of the image, then restart part way through. Looking at the logs, I see the following entries repeating every 1-30 minutes:
28.11.18 10:47:52 (-0500) Service is already running ‘main sha256:cf22d03cf9a898f168209d74be6d27d0c7d67e85c8b6b4fb40533b6179882f8d’
28.11.18 10:47:54 (-0500) Downloading image ‘registry2.balena-cloud.com/v2/9995b4b712e0a603f6bd2e1f842a6ccc@sha256:61286a5a579d56c7218902f918cf0615e11bfe935c8f4bf77c3334ad4dfd9b09’
While the device is update it is not using the new version. It is running the existing version of the app. I pushed a new version with a whitespace only change.
We checked the status of our registry hosts around this time, and nothing was revealed on that side of things. Either way I’m inclined to believe that this was a network hiccup and that you’re upgrading of the device was orthogonal to the image eventually being downloaded.
That being said if you see this again, we’d really like to take a look at the device as it’s occurring, to ensure that was indeed the case.