supervisor: "Supervisor is not privileged" even though it is
Describe the issue
Supervisor panel suddenly reports that my system is unhealthy due to “Supervisor is not privileged”
When I check the supervisor container it says that it is:
Steps to reproduce
- …
- …
- …
Enviroment details
- Operating System:: xxx
ha host info
chassis: desktop
cpe: ""
deployment: ""
disk_free: 18.8
disk_total: 62.3
disk_used: 40.2
features:
- reboot
- shutdown
- services
- network
- hostname
hostname: adloko
kernel: 5.4.0-53-generic
operating_system: Ubuntu 18.04.5 LTS
- Supervisor version:: xxx
arch: amd64
channel: stable
debug: false
debug_block: false
diagnostics: null
healthy: false
ip_address: 172.30.32.2
logging: info
supported: false
timezone: Europe/Berlin
update_available: false
version: 2020.12.2
version_latest: 2020.12.2
wait_boot: 5
- Home Assistant version: xxx
arch: amd64
channel: stable
docker: 19.03.13
features:
- reboot
- shutdown
- services
- network
- hostname
hassos: null
homeassistant: 0.118.4
hostname: adloko
logging: info
machine: qemux86-64
operating_system: Ubuntu 18.04.5 LTS
supervisor: 2020.12.2
supported: false
supported_arch:
- amd64
- i386
timezone: Europe/Berlin
Supervisor logs
Supervisor logs
20-12-04 16:43:40 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
20-12-04 16:43:57 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
20-12-04 16:48:15 WARNING (MainThread) [supervisor.jobs] 'AddonManager.install' blocked from execution, system is not healthy
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (4 by maintainers)
So, whenever a supervisor update arrives the system becomes automatically unhealthy now for “unsupported” systems?
I found HA multiple times in the last week or so with all addons suddenly disabled and no hint why I could not update one (update button just flashed red with no indication why). Only then I went to look for issues elsewhere. There could be at least some kind of notification when the system gets flagged as unhealthy when it was previously ok.
I know that I’m running an unsupported installation but the spontaneous nature of supervisor updates are real liability to system stability. Installing them at any time leaves you at risk of breaking peoples systems (see introduction of DNS features) . It is ok if things have breaking changes, occasional bugs, or have additional hoops to jump through in case of unsupported systems, but those “fixing periods” need to be plannable. I don’t want to worry every morning whether things broke overnight. I want to move updates to weekends when I can spend the time.
So, the solution would be quite simple: There should be an option to opt-out of automatic supervisor updates.