To clear Supervisors marked unhealthy from this incident, a Supervisor restart is enough. You can do this ha supervisor restart. To restart the complete system, you can also reboot the OS using ha host reboot.
If the system remains unhealthy, it is probably for a different reason.
I am running supervisor 2024.11.3. Had no issues when updating.
So now my backups are made with this version of the supervisor.
The issue: you cannot restore a backup made with 2024.11.3 on a system with supervisor 2024.11.2.
I am experiencing this issue right now because I was in the process of moving Home Assistant to new hardware. This seems to be impossible right now because I cannot restore my backup on the new system. Since supervisor 2024.11.3 was pulled I cannot update the new system to it and I am stuck.
Is there a way around this? If not, people running 2024.11.3 are currently producing backups that cannot be restored on newly installed systems.
Sadly no. Only thing I’ve found out, that issue is with google changing something with login authentication. Apparently for some users setting youtube accounts as brand helped with issue.
Yes, this is currently an issue. You can work around by switching to beta channel on the new installation: Use ha su options --channel beta, then ha su reload and ha su update. This will update to the Supervisor version 2024.11.3, and allows to restore the backup.
To be clear, the 2024.11.3 release is just fine. The problem we have is with the rollout procedure overloading ghcr.io. So it is perfectly fine to switch to beta channel (and back to stable after the update) simply to get this Supervisor version.