core: Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy

The problem

After I install Supervisor 2022.10.0 I can not update HA core from 2022.10.1 to 2022.10.2

[2803511008] Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 303, in async_install
    await async_update_core(self.hass, version=version, backup=backup)
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 45, in _wrapper
    raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: 'HomeAssistantCore.update' blocked from execution, system is not healthy

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 202, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 207, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 154, in async_install
    await entity.async_install_with_progress(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 413, in async_install_with_progress
    await self.async_install(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 305, in async_install
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Error updating Home Assistant Core 'HomeAssistantCore.update' blocked from execution, system is not healthy

What version of Home Assistant Core has the issue?

2022.10.1

What was the last working version of Home Assistant Core?

2022.10.1

What type of installation are you running?

Home Assistant Container

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

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (2 by maintainers)

Most upvoted comments

@ludeeus - your close message is unhelpful and disrespectful of the OP and other’s issue. If you’re going to close an issue, you should at least explain the actual problem. In my case the system is complaining about the fact that docker is installed. Indeed docker-ce version 20.10.18 is installed and running. In fact I have everything listed in the requirements for a supervised system.

For the end-user, it’s not clear what constitutes ‘unhealthy’ from this message, particularly when updating Home Assistant in this way as it has not been a problem until now.

Aside from that, it seems that running portainer as an addon through Home Assistant is more ‘healthy’ (it works). Can we rely on this, or can we expect this route to also be shut down in future?

Your system is unhealthy, it’s expected to fail. You need to make sure that the system is in a healthy state.

I have the same problem: having portiner running on the same machine makes system unhealthy and unable to update. This is something really weird. Portainer doesn’t stop/run/update containers on it’s own, so it’s not more dangerous to HA than just having docker and bering able to do the same things in the console. This is extremely overprotective, we need at least to be able to turn off this “functionality” with some kind of configuration.

Yes. 18 days ago portainer add to unhealthy list.

https://github.com/home-assistant/supervisor/commit/262fd05c6d3136dba50eb9c8fb69da4f178b8d5b

Its very strange design.