As with the other posts (e.g. here, here, here, and here) – apparently the HAOS 14.1 upgrade bricked my Proxmox VM – yet it seems to be a different error, that’s why I’m writing another post.
So, I get tons of this in the logs (journalctl in the “emergency prompt”):
# both are originally one line – broken up for readability
AVC apparmor="denied" operation="mkdir" class ="file" profile="hassio-supervisor"
name="/usr/local/lib/python3.12/site-packages/jinja2/__pycache__"
comm="python3" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
# next line
SYSCALL arch=c000003e syscall=83 success=no exit=-13
a0=7f66e3c92e70 comm=python3 exe="/usr/local/bin/python3.12"
subj=hassio-supervisor key=(null)
# ... and now repeat those two a LOT of times ...
Some notes:
- the Proxmox VM was created using “proxmox-helper-scripts” not two months ago
- I tried updating the OS before Home Assistant by hitting “Update” in the iOS app’s UI
- when restarting, I get two “slots” in the boot manager – both fail to start like this:
Waiting for the Home Assistant CLI to be ready... [WARN] Home Assistant CLI not starting! Jump into emergency console... - the
hacommand does not work in the shell:# ha Error response from daemon: No such container: hassio_cli
Can anyone help? maybe I just have to create that dir … but … which one?!
(also – lesson learned: remember to never hit “upgrade” in out of a whim again without a VM backup …)