Update to 0.110.5 failing constantly

[chri5tian (Chris Tian)]

Hello everyone. I am running Hassio in Docker on a Synology NAS, until now it’s been working fine.
I’ve been trying to update my Home Assistant to 0.110.5, I am currently on 0.109.6, everything seems to go well but then I am still presented with the update screen saying I’m still on 0.109.6. I tried performing the update via CLI as well:

Here are the logs I found after Home Assistant came back online:

20-06-08 17:20:23 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for core_ssh
20-06-08 17:20:26 INFO (SyncWorker_9) [supervisor.docker.addon] Start Docker add-on homeassistant/amd64-addon-ssh with version 8.5.4
20-06-08 17:20:30 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.10:8099 ssl:None [Connection refused]
20-06-08 17:21:12 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for a0d7b954_ssh
20-06-08 17:21:14 INFO (SyncWorker_9) [supervisor.docker.addon] Start Docker add-on hassioaddons/ssh-amd64 with version 7.4.0
20-06-08 17:21:16 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_ssh
20-06-08 17:21:18 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:62364 ssl:None [Connection refused]
20-06-08 17:22:03 INFO (SyncWorker_3) [supervisor.docker.interface] Clean addon_core_ssh application
20-06-08 17:22:03 INFO (SyncWorker_3) [supervisor.docker.interface] Remove image homeassistant/amd64-addon-ssh with latest and 8.5.4
20-06-08 17:22:04 INFO (MainThread) [supervisor.addons.addon] Remove add-on data folder /data/addons/data/core_ssh
20-06-08 17:22:04 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for core_ssh
20-06-08 17:22:04 INFO (MainThread) [supervisor.addons] Add-on ‘core_ssh’ successfully removed
20-06-08 17:22:25 INFO (MainThread) [supervisor.api.security] /core/update access from a0d7b954_ssh
20-06-08 17:22:25 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.5
20-06-08 17:22:25 INFO (SyncWorker_8) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.109.6 to homeassistant/qemux86-64-homeassistant:0.110.5
20-06-08 17:22:25 INFO (SyncWorker_8) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.5.
20-06-08 17:25:00 INFO (SyncWorker_8) [supervisor.docker.interface] Stop homeassistant application
20-06-08 17:26:02 INFO (SyncWorker_8) [supervisor.docker.interface] Clean homeassistant application
20-06-08 17:26:02 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-06-08 17:26:04 INFO (SyncWorker_6) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.110.5
20-06-08 17:26:24 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-06-08 17:26:48 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-06-08 17:28:29 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-06-08 17:38:30 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!
20-06-08 17:38:30 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-06-08 17:38:30 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.109.6
20-06-08 17:38:30 INFO (SyncWorker_8) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.110.5 to homeassistant/qemux86-64-homeassistant:0.109.6
20-06-08 17:38:30 INFO (SyncWorker_8) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.109.6.
20-06-08 17:39:03 INFO (SyncWorker_8) [supervisor.docker.interface] Stop homeassistant application
20-06-08 17:39:08 INFO (SyncWorker_8) [supervisor.docker.interface] Clean homeassistant application
20-06-08 17:39:08 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-06-08 17:39:09 INFO (SyncWorker_19) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.109.6

I tried disabling most add-ons, no luck.
Has anyone experienced something similar? On another thread I saw they were mentioning an issue with PulseAudio, I see some supervisor messages but no errors.
I also uninstalled everything, reinstalled Hassio in Docker and restored from a backup, it goes back to 0.109. If I choose to restore without restoring Home Assistant, it never comes back online.
I’ve been trying to update for the last 3 days, no luck.

Any idea what could go wrong, anyone?
Thanks

[VDRainer]

Take a look in the HA start log.

0.110: Speed! OpenZWave beta, HomeKit Cameras, ONVIF, Calendars

That’s the question of the day! As a venv user with --log-rotate-days option i would simply look at the home-assistant.log file. I tried to replicate this on my VBox HassOS. Install the SSH & Web Terminal Addon, disable protection mode. Open up two SSH Sessions, don’t use the Web Terminal, use another ssh client like putty. In the first terminal start docker logs -f hassio_supervisor this will show the log of the supervisor In the second one only type (don’t press…

[chri5tian (Chris Tian)]

Thanks VDRainer, I did that, supervisor logs not giving me much help, same message:

20-06-09 00:06:40 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!
20-06-09 00:06:40 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!

Looking at the docker logs -f homeassistant output I couldn’t figure out anything obvious either apart from a few error messages which I corrected in the config (like duplicate keys or getting rid of some unused configuration for esphome or credentials for shelly devices), but still didn’t help updating when I tried again the next time.

I will try one more time tomorrow and go through the logs again, in case there is something escaping me, but so far nothing obvious.

[chri5tian (Chris Tian)]

Finally cracked it, someone in another thread mentioned ONVIF creating problems when updating, I went through my configuration and found some old ONVIF code in configuration.yaml. I removed it and tried updating one more time and this time it worked straight away. After the update I received a notification about the manual alarm panel, I guess I’ll have to look at it, as it seems to be one of the breaking changes, however it seems it wasn’t the cause of my update failure.