Unable to upgrade Hassio

Installation Home Assistant OS
1

I’m trying to upgrade from 102.3 to 103.2, but the upgrade failes. Any ideas why?

19-12-19 13:30:10 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.103.2
19-12-19 13:30:10 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.102.3 to homeassistant/raspberrypi3-homeassistant:0.103.2
19-12-19 13:30:10 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.103.2.
19-12-19 13:31:00 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-12-19 13:31:00 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-12-19 13:31:24 INFO (MainThread) [hassio.store] Load add-ons from store: 62 all - 0 new - 0 remove
19-12-19 13:37:21 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.103.2 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.103.2: No such image: homeassistant/raspberrypi3-homeassistant:0.103.2").
19-12-19 13:37:21 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
19-12-19 13:37:21 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<process_lock.<locals>.wrap_api() done, defined at /usr/src/hassio/hassio/utils/__init__.py:20> exception=HomeAssistantUpdateError()>
Traceback (most recent call last):
  File "/usr/src/hassio/hassio/utils/__init__.py", line 29, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/src/hassio/hassio/homeassistant.py", line 337, in update
    raise HomeAssistantUpdateError()
hassio.exceptions.HomeAssistantUpdateError
1 Like
2

I often get this error.

"no such image: homeassistant/raspberrypi3-homeassistant:0.103.2: No such image: homeassistant/raspberrypi3-homeassistant:0.103.2"

I read in a topic it has something to do with the hassio-supervisor not having the right time, but as for as I can tell mine has the correct time. Last time after 20 times hitting the update button it finally worked.

3

Very strange. If I do…

 docker pull homeassistant/raspberrypi3-homeassistant:0.103.2

…on another computer, the package starts downloading. So it’s definitely there.

4 
19-12-19 13:14:45 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/raspberrypi-homeassistant tag 0.103.2.
19-12-19 13:14:45 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/raspberrypi-homeassistant:0.103.2 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:34226->[::1]:53: read: connection refused").
19-12-19 13:14:46 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
19-12-19 13:15:27 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.103.2
19-12-19 13:15:27 INFO (SyncWorker_2) [hassio.docker.interface] Update image homeassistant/raspberrypi-homeassistant:0.103.0 to homeassistant/raspberrypi-homeassistant:0.103.2
19-12-19 13:15:27 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/raspberrypi-homeassistant tag 0.103.2.
19-12-19 14:29:26 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/raspberrypi-homeassistant:0.103.2 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi-homeassistant:0.103.2: No such image: homeassistant/raspberrypi-homeassistant:0.103.2").
5

For those who did update successfully, how long did it take? I’m running 0.100.3 on a Pi3B+. I’m trying to update to 0.103.2 as the others in this thread. I’m just trying to figure out how long it should take.

6

I’m getting the same error on a new install of 3.7. In my case all I see on the web UI is
Preparing Hass.io (this can take up to 20 minutes) I left it run overnight and the status remains the same.

This problem is has been driving me crazy for the past few days, but I just found the supervisor logs this morning. As far as I can tell my time is correct, although I can’t find any trace of ntp or chrony so I can’t vouch for the time being within milliseconds.

Interestingly enough, I pulled the container manually on the pi3 and it had no problem downloading it… so obviously the file is there. I did get an error saying /usr/local/lib/blah.blah.blah was full. I checked it out and the root volume is only 91M and 100% full. Kind of surprised /usr isn’t mounted as a separate partition.

7

I have the same issue… I tried to update lot of time without success
Following the log captured on the system window:

19-12-23 13:53:42 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.103.4
19-12-23 13:53:42 INFO (SyncWorker_9) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.102.1 to homeassistant/raspberrypi3-homeassistant:0.103.4
19-12-23 13:53:42 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.103.4.
19-12-23 13:57:39 ERROR (SyncWorker_9) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.103.4 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.103.4: No such image: homeassistant/raspberrypi3-homeassistant:0.103.4”).
19-12-23 13:57:39 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Any idea to fix it ?
Thanks

8

Just try again. I always get this message trying to upgrade. After the n-th time it usually works.

9

This version wouldn’t work transparently with my 0.102.3 configs. It messed me up for a while because I was migrating hosts (from a PC to a Pi). I had just pulled “latest” in docker on the Pi and assumed everything would work. It was loading the person module and not showing any of my custom_components.mitsubishi_mqtt.

10

I tried several times (50+) without success :frowning_face:
I will wait for the next version

11

I rebooted my raspi and now I was able to upgrade…