Seems like something is missing in the 101.3 release. 6 days later I’m still having the same issue as OP in trying to update my hassio install.
19-11-14 12:00:51 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.3
19-11-14 12:00:51 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.101.2 to homeassistant/qemux86-64-homeassistant:0.101.3
19-11-14 12:00:51 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.101.3.
19-11-14 12:01:15 ERROR (SyncWorker_3) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.101.3 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.101.3: No such image: homeassistant/qemux86-64-homeassistant:0.101.3").
19-11-14 12:01:15 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
I’ve never had any issues updating through hassio before. Not sure whats going on here.
I guess I’m slightly different… I try to start the update, the button kind of spins, then it just gives up. My home assistant and hassio never even restart. I just pulled these lines from the hass io system log.
Same log entries, but my hass instance stays running & accessible.
It fails and rolls back to 0.100.3, then simply restarts and works as before.
19-11-14 13:38:43 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-11-14 14:32:03 INFO (MainThread) [hassio.host.info] Update local host information
19-11-14 14:32:03 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-11-14 14:32:04 INFO (MainThread) [hassio.host.services] Update service information
19-11-14 14:32:04 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-11-14 14:32:05 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-11-14 14:32:05 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-11-14 14:53:15 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.3
19-11-14 14:53:15 INFO (SyncWorker_2) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.100.3 to homeassistant/raspberrypi3-homeassistant:0.101.3
19-11-14 14:53:15 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.101.3.
19-11-14 14:59:15 INFO (SyncWorker_2) [hassio.docker.interface] Stop homeassistant application
19-11-14 15:00:19 INFO (SyncWorker_2) [hassio.docker.interface] Clean homeassistant application
19-11-14 15:00:22 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.101.3
19-11-14 15:00:57 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-11-14 15:01:42 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-11-14 15:11:45 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-11-14 15:11:45 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-11-14 15:11:45 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.100.3
19-11-14 15:11:45 INFO (SyncWorker_19) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.101.3 to homeassistant/raspberrypi3-homeassistant:0.100.3
19-11-14 15:11:45 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.100.3.
19-11-14 15:11:47 INFO (SyncWorker_19) [hassio.docker.interface] Stop homeassistant application
19-11-14 15:11:50 INFO (SyncWorker_19) [hassio.docker.interface] Clean homeassistant application
19-11-14 15:11:51 INFO (SyncWorker_5) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.100.3
19-11-14 15:12:16 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-11-14 15:13:06 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-11-14 15:13:41 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-11-14 15:13:41 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.100.3
19-11-14 15:13:42 INFO (SyncWorker_5) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-homeassistant:0.101.3']
19-11-14 15:16:11 INFO (SyncWorker_18) [hassio.docker.interface] Stop addon_7ad98f9c_zigbee2mqtt application
19-11-14 15:16:12 INFO (SyncWorker_18) [hassio.docker.interface] Clean addon_7ad98f9c_zigbee2mqtt application
19-11-14 15:16:15 INFO (SyncWorker_6) [hassio.docker.addon] Start Docker add-on dwelch2101/zigbee2mqtt-armhf with version 1.4.0
19-11-15 13:31:00 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.3
19-11-15 13:31:00 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.100.2 to homeassistant/qemux86-64-homeassistant:0.101.3
19-11-15 13:31:00 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.101.3.
19-11-15 13:31:46 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.101.3 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.101.3: No such image: homeassistant/qemux86-64-homeassistant:0.101.3").
19-11-15 13:31:46 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
Created symlink /etc/systemd/system/multi-user.target.wants/hassio-supervisor.service → /etc/systemd/system/hassio-supervisor.service.
[Info] Install AppArmor scripts
Created symlink /etc/systemd/system/multi-user.target.wants/hassio-apparmor.service → /etc/systemd/system/hassio-apparmor.service.
[Info] Run Hass.io
… but once this completes, the final setup stalls as it gets into a loop.
When I look in Portainer, at the output from the supervisor, I’m seeing a lot of 404s …
19-11-15 18:20:55 ERROR (SyncWorker_14) [hassio.docker.interface] Can't install homeassistant/intel-nuc-homeassistant:0.101.3 -> 404 Client Error: Not Found ("no such image: homeassistant/intel-nuc-homeassistant:0.101.3: No such image: homeassistant/intel-nuc-homeassistant:0.101.3").
I tried to use qemux86, but get similar.
19-11-15 19:16:24 WARNING (MainThread) [hassio.homeassistant] Error on install Home Assistant. Retry in 30sec,
19-11-15 19:16:54 INFO (SyncWorker_16) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:landingpage to homeassistant/qemux86-64-homeassistant:0.101.3,
19-11-15 19:16:54 INFO (SyncWorker_16) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.101.3.,
19-11-15 19:17:17 ERROR (SyncWorker_16) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.101.3 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.101.3: No such image: homeassistant/qemux86-64-homeassistant:0.101.3").
19-11-19 10:55:29 INFO (MainThread) [hassio.snapshots] Full-Snapshot d2fa9c33 done
19-11-19 10:56:02 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.3
19-11-19 10:56:03 INFO (SyncWorker_16) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.100.3 to homeassistant/raspberrypi3-homeassistant:0.101.3
19-11-19 10:56:03 INFO (SyncWorker_16) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.101.3.
19-11-19 11:01:23 INFO (SyncWorker_16) [hassio.docker.interface] Stop homeassistant application
19-11-19 11:02:25 INFO (SyncWorker_16) [hassio.docker.interface] Clean homeassistant application
19-11-19 11:02:30 INFO (SyncWorker_7) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.101.3
19-11-19 11:03:05 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-11-19 11:03:51 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-11-19 11:13:54 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-11-19 11:13:54 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-11-19 11:13:54 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.100.3
19-11-19 11:13:54 INFO (SyncWorker_3) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.101.3 to homeassistant/raspberrypi3-homeassistant:0.100.3
19-11-19 11:13:54 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.100.3.
19-11-19 11:13:58 INFO (SyncWorker_3) [hassio.docker.interface] Stop homeassistant application
19-11-19 11:14:01 INFO (SyncWorker_3) [hassio.docker.interface] Clean homeassistant application
19-11-19 11:14:02 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.100.3
19-11-19 11:14:27 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress
19-11-19 11:15:18 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done
19-11-19 11:15:48 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-11-19 11:15:48 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.100.3
Ok, I finally fixed it.
For reference, I had to comment api_password: line.
I was not using it, but it was still there.
I read in the changelog that api_password was not supported anymore, but I didn’t know that it could block the upgrade process.
Now I’m on 0.101.3.
If you had API password set up under http: in your config, you either have to remove it or move it under auth_providers (which is under homeassistant:) before updating to 0.101.
But it’s going to be removed entirely sometime in the future, so moving it under auth_providers isn’t the best idea anyway.