Core: 0.110.4 isn't being built / released

[hmmbob]

The problem

0.110.4 was released yesterday, but hasn't been released in Docker Hub. Looks like the pipeline hasn't picked up the merge.

I commented in the PR, but realized later that that isn't the correct place 😉

Environment

All n/a

• Home Assistant Core release with the issue:
• Last working Home Assistant Core release (if known):
• Operating environment (Home Assistant/Supervised/Docker/venv):
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

[anup92k]

Hello,
Got the same issue on PIP.
The PyPI page of HA doesn't show the new release either.

[Scialla]

[foglietti]

I have the same problem.

[hmmbob]

It's not a problem on your side, the builds are just not made automatically, probably due to a glitch. As soon as one of the core devs kick-off the release pipeline everything should be available within 90-120 mins or so.

Nothing you can do on your side, except for waiting patiently :smile:

[frenck]

We are looking into this, currently no ETA.

@hmmbob PS, the merge does not trigger the pipelines 😉

[hmmbob]

@frenck Oh, really? I thought that was fully automated based on the tagging. My bad 😄

[frenck]

Yes, it is based on tagging, not merging 😄

[frenck]

Builds have been fixed/triggered and are running. It should be available for everybody in around 2 hours from the time of writing this message.

PyPi release is already available.

[Taomyn]

Sorry if this is not the correct place to ask, but should I be able to "ha core update --version" this release like I did for 0.110.3? I had the same when it was previously announced.

I get this logged

20-05-30 08:19:21 INFO (MainThread) [supervisor.api.security] /core/update access from a0d7b954_ssh
20-05-30 08:19:21 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.4
20-05-30 08:19:21 INFO (SyncWorker_5) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.110.3 to homeassistant/qemux86-64-homeassistant:0.110.4
20-05-30 08:19:21 INFO (SyncWorker_5) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.110.4.
20-05-30 08:19:42 ERROR (SyncWorker_5) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.110.4 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.110.4: No such image: homeassistant/qemux86-64-homeassistant:0.110.4").
20-05-30 08:19:42 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
20-05-30 08:19:49 INFO (MainThread) [supervisor.api.security] /core/info access from a0d7b954_ssh

[frenck]

@Taomyn 404 usually means a diskspace issue.

The image is available:

[Taomyn]

@frenck thanks, I hadn't increased the size of the VM since I installed it last week and it was almost full as you suspected - glad it saw the new space and automatically expanded. Surprised not to see a disk space indicator anywhere within the various UI info but it's fixed now and updated.