As per ADR-0014;
Debian Linux Debian 11 aka Bullseye (no derivatives)
There is a couple of open bug reports currently, this issue may be one of them. Hopefully the HA team will address it quickly.
1 Like
I hope it is fixed soon,
I am currently without HA, I deleted the previous system because I thought I could reinstall, but I did not think there would be this bug ā¦
Install HA OS or Container then
But I want a supervised installation
HA OS is Supervised, without the underlying OS control. For what specific reason do you need access to the OS ?
@kanga_who My network operates with a private security certificate,
And because of this I need to install the security certificate of my network inside the system,
I tried the HA OS system but without the installation it does not allow me secure network access,
Therefore I need access to the operating system
Well you have 2 choices for now then, have no HA, or install Container.
edit:
Do you mean ssl certificates?
The logic is clear ā¦
Based on past events Do you have an estimate of how long it will take to fix this?
From this I will decide whether I will wait or go on Container.
Iām talking about ca.crt certificates that tell the OS that you can trust an SSL certificate that the external network sends,
(If you know of another way to install the credentials that also works in HA OS I would love to hear)
I assume you tried putting the certs in the /root/ssl folder?
I just followed this guide yesterday to reinstall HA 2022.6.X and the end result showed āUnsupportedā due to āDocker configurationā. I verified that the Docker logging is set up correctly, so Iām assuming itās related to the cgroup issues noted elsewhere in this thread. Iām also assuming that the HA installation script which is run as part of this guide will be updated at some point to account for the necessary cgroup changes.
@kanga_who I tried and it did not help, it should be installed in the operating system itself,
Apparently the SSL folder does not affect the system itself,
System Health
| version | core-2022.7.0 |
|---|---|
| installation_type | Home Assistant Supervised |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.5 |
| os_name | Linux |
| os_version | 5.15.32-v8+ |
| arch | aarch64 |
| timezone | Europe/Kiev |
| config_dir | /config |
Home Assistant Supervisor
| host_os | Debian GNU/Linux 11 (bullseye) |
|---|---|
| update_channel | beta |
| supervisor_version | supervisor-2022.06.2 |
| agent_version | 1.2.2 |
| docker_version | 20.10.17 |
| disk_total | 56.8 GB |
| disk_used | 9.8 GB |
| healthy | true |
| supported | true |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Log Viewer (0.14.0), MariaDB (2.4.0), Studio Code Server (5.1.1), File editor (5.3.3), Mopidy (2.1.1) |
Raspberry Pi OS 64 bit (BullsEye)
Does Raspberry Pi OS support boot from SSD?
@Patrick010 @meni123 and others who had issues with Network Manager, it looks as thought eh PRs to fix that issue have been merged to fix the Debian 11.3 issue.
11.4 released on the weekend. does it require this fix? I have never seen an issue anyway. Is it only on installation?
@kanga_who My problem still exists,
In the installation I get the error
[warn] Could not find / etc/ default/ grub or / boot/cmdline. txt failed to switch to cgroup vl
Check if cmdline.txt exists in /boot/firmware. If so add systemd.unified_cgroup_hierarchy=false lsm=apparmor
Be also sure apparmor is installed.
I sub mitted a PR to have apparmor added to the dependencies for install and was told, after testing by one of devs, that it ships natively so wasnāt required. Seems like that may not be the case.
I think I will add it back to dependencies.
I did as you wrote and managed to get a supervised supervisor, but I started getting this error every few minutes! Does it have anything to do with it?
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 334, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"