supervisor: Unhealthy State / Unsupported OS
Describe the issue
Addon installs/changes/deletes, and supervisor upgrades blocked due to “unhealthy state”. Investigating the errors/links provided by HASS showed a list of docker issues. These were all checked and are passing on my system (docker is latest version, no extra containers, etc). Additional messages state “unsupported OS”. I’m running HASS Supervisor on a bare metal Arch Linux install, and have been for just under 18 months.
Steps to reproduce
Attempt to install or remove any addons. Attempt to update or downgrade HASS Supervisor/core.
Enviroment details
Version 2020.12.2 Newest Version 2020.12.2 Channel stab Hostname hass.redactedyo.io IP Address 172.20.0.40/23 Operating System Arch Linux Linux hass.redactedyo.io 5.9.11-arch2-1 #1 SMP PREEMPT Sat, 28 Nov 2020 02:07:22 +0000 x86_64 GNU/Linux Docker version 19.03.14-ce le
Supervisor logs
Supervisor logs
20-12-02 23:12:23 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
20-12-02 23:12:24 WARNING (MainThread) [supervisor.resolution.evaluations.base] Detected unsupported OS: Arch Linux (more-info: https://www.home-assistant.io/more-info/unsupported/os)
20-12-02 23:12:24 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
20-12-02 23:12:24 INFO (MainThread) [__main__] Running Supervisor
20-12-02 23:12:24 WARNING (MainThread) [supervisor.core] System running in a unsupported environment!
20-12-02 23:12:24 CRITICAL (MainThread) [supervisor.core] System running in a unhealthy state and need manual intervention!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (7 by maintainers)
I run Ubuntu on one of my systems and does not have issues
But this is however expected, and not a bug. In the UI (under the unsupported message in the “Supervisor” card in my screenshot) there will be a similar text for unhealthy with a dialog that provides links to how you can fix the system.
I’ll also add that if this suffix is the issue, the version of docker itself is operating fine, and a string difference should certainly not introduce a broken state on a production system.
Likely related to #2334 #2330 and probably a bunch of other incoming ones. Seems to be affecting everyone who doesn’t run HASSOS.
I did find a temporary workaround by adding
{"ignore_conditions": ["healthy"]}tojobs.jsonin my HASS supervisor directory. I posted this in a forum with a CRUSHINGLY MASSIVE WARNING TO ANYONE WHO TRIES THIS THAT IT SHOULD ONLY BE USED TO PUT THE SYSTEM IN A STATE WHERE YOU CAN ACTUALLY FIX IT and that applies here too.