ET dans les infos de l’issue ils expliquent pourquoi ça a disparu, pour mieux revenir
What happened
We changed the Supervisor update a while ago to make Supervisor update as soon as it learns about the update (see #5375). This was an intentional change, which has been tested since a couple of weeks, and rolled out already last week to stable.
Today’s release was the first time where this new update mechanism got used when we published a new version to stable. The update had the side effect that updates rolled out within a 2h window (instead of 8h window), which was not handled well by the GitHub container registry (causing all the
toomanyrequests).What is the fix
The latest version of Supervisor has been pulled from Supervisor about 2h ago, which means that you should no longer see the update notification. So for most users, the errors in the logs should stop from appearing and the update notification disappears on it’s own.
For users who have rebooted the system in the last ~8h they also see a message « Unhealthy system - Supervisor update failed ». This message appears because despite a good network connection, we were not able to update the Supervisor. Another reboot of the system should make this message disappear as well.
What if I updated successfully
If you successfully updated to Supervisor 2024.11.3, that is fine too. The version itself is fine. The system won’t rollback. We’ll eventually release a new version of Supervisor so you’ll have the same stable version as anyone else.
What happens from now
We are currently working on solutions to rollout the new Supervisor version without hitting the rate limit.