I can no longer update my home assistant core 2022.4.1

[hanskulker]

The problem

I can no longer update my home assistant core. My last installed version is core-2022.4.1 and it still works fine. I can't install 4.2 and 4.3 and 4.4. My system is a NUC with Debian 11 and supervisor-2022.04.0 It is also no longer possible to perform apt update, this gives a temporary error when looking up deb.debian.org The log file keeps showing the following error: ERROR (MainThread) [supervisor.store.repository] Can't remove built -in repositories!

I also tried a fresh install on my backup system. This is no longer possible . This gives no error messages until after the installation, but homeassistant cannot be started in the docker container.
Also it is no longer possible to perform apt update this gives temporary error when looking up deb.debian.org

What version of Home Assistant Core has the issue?

core-2022.4.2 and higher

What was the last working version of Home Assistant Core?

core-2022.4.1

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[hanskulker]

The installation is done according to the link https://github.com/home-assistant/supervised-installer

The execution of the command seems good of wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb dpkg -i homeassistant-supervised.deb

But the installation did not work and has been modified in such a way that Debian can no longer be updated and no new programs can be installed

[Veldik]

I had same issue on same version. I fixed by resetting dns servers in /hassio/system. I dont know why DNS wasn't set.

[hanskulker]

Jakub,

Can you clarify how I should do that.

This may not yet solve the problem of the new installation.

[hanskulker]

Dit is de foutmelding die ik krijg. 22-04-18 10:56:08 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2022.4.5 22-04-18 10:56:08 INFO (SyncWorker_7) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.1 to ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.5 22-04-18 10:56:08 INFO (SyncWorker_7) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2022.4.5. 22-04-18 10:56:09 ERROR (SyncWorker_7) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.5: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2022.4.5&fromImage=ghcr.io%2Fhome-assistant%2Fqemux86-64-homeassistant&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io on [::1]:53: read udp [::1]:56025->[::1]:53: read: connection refused") 22-04-18 10:56:09 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed

[dennisbrouwer91]

Same issue here on 2022.4.1! Any fix found yet?

[tdejneka]

Same problem. Posting in Supervisor repo because this appears to be an issue with supervisor, not Core.

[hanskulker]

It seems that the problem is in the Network manager settings. Settings are adjusted with regard to the IP address and the DNS. I tried to adjust settings but it is immediately restored with a new file with the old settings on startup. In this folder /etc/NetworkManager/system-connections I don't have enough knowledge to investigate further.

[hanskulker]

The problem that is in the settings of the Network Manager cannot be solved with my knowledge. Since there is no solution to the problem so far, I decided to do a reinstall. I did the reinstallation entirely with a dynamic IP address. After everything worked well, including restoring the backup, I set it to a fixed IP address via Gui, settings, supervisor, system, Host

[tdejneka]

A bug that forces the user to re-install, what was previously a perfectly functional system, is a nasty bug.

[tdejneka]

FYI

Here's how I resolved this problem:

https://github.com/home-assistant/supervisor/issues/3582#issuecomment-1107517238

[hanskulker]

Unfortunately Unfortunately after a fresh install it seemed to work fine. Tried to update from 2022-4-6 to 7 this morning but again the error below.

22-04-25 11:48:07 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2022.4.7 22-04-25 11:48:07 INFO (SyncWorker_4) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.6 to ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.7 22-04-25 11:48:07 INFO (SyncWorker_4) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2022.4.7. 22-04-25 11:48:23 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2022.4.7: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2022.4.7&fromImage=ghcr.io%2Fhome-assistant%2Fqemux86-64-homeassistant&platform=linux%2Famd64: Internal Server Error ("Head "https://ghcr.io/v2/home-assistant/qemux86-64-homeassistant/manifests/2022.4.7": Get "https://ghcr.io/token?scope=repository%3Ahome-assistant%2Fqemux86-64-homeassistant%3Apull&service=ghcr.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers)") 22-04-25 11:48:23 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed.

Help Help

[hanskulker]

I was probably too early to update. Probably problems with the update server. Tonight it worked. apologies for responding too early.

[mdegat01]

So there was a particularly bad bug around handling of network settings that went unnoticed for a while. Basically when network settings were updated from supervisor it blew away all custom network manager configurations it did not understand for the network interfaces it managed (which is a lot, network manager has many options).

This problem was discovered in 2022.4.0 by #3528 since we auto-applied an update in order to apply current defaults for everyone with out of date configurations. The issue has since been fixed in #3570 but that won't restore what was lost it will simply keep it from being lost again.

Reading how @tdejneka solved it here makes me think this is a symptom of #3528 . But the one thing I'm not understanding is how the DNS server information could've been lost. That is a setting that supervisor understands, it should show up in the network information of the supervisor panel and when you run the ha network info command.

If the issue is simply the DNS server is missing you should be able to tell from the network info in the supervisor info panel and you should be able to fix it from there as well. If adding a DNS server there does not actually set the DNS server for your network interface then please let me know as that is a bug that needs to be fixed.

Also if anyone is on the beta for 2022.5 then my supervisor info panel link won't work since network information moved. Instead you'll need to go to Configuration -> System -> Network. Sorry I can't make a my link for that yet since its not out yet.

[esdcmc]

I don't know if this is of any help but I couldn't fix my Home Assistant refusing to update problem (with ghcr.io error), until I found that under

• Settings
• System
• Network
• Configure Network Interfaces
• IPv4

the DNS servers field was blank

My HA server uses static IP connection with specific Gateway address that needs to be repeated for DNS server.

This was my default configuration eth0 under Linux but recently the HA supervisor has taken over but 'forgot' the DNS server.

Missing updates were not the only problem, HA also showed the wrong time, and I found that part of the system behaved as if Internet was disconnected.

FINAL OBSERVATION Linux advanced network configuration seems to pile up more that one configuration called 'Supervisor Eth0' (or something like that). Is it normal?

[ausfestivus]

I can confirm I am seeing the same behaviour. You can see some information here https://discord.com/channels/330944238910963714/944337294389805056/990871542634262588.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.