supervisor

Home-Assistant/supervisor

Fork 0

mirror of https://github.com/home-assistant/supervisor.git synced 2026-08-18 02:43:18 +01:00

Files

T

History

312e0c0e78 Only report systemd unit failures to Sentry on Home Assistant OS (#7009 )

* Only run systemd unit failure check on Home Assistant OS

The systemd unit failure check added in #6976 creates a repair issue and
reports to Sentry for any failed unit on the host. On supervised
installations the first week of the 2026.07.0 rollout surfaced failed
units like gdm.service, tomcat8.service or isc-dhcp-server.service which
are unrelated to Home Assistant and not actionable for us. Skip the
check entirely when not running on Home Assistant OS, like the multiple
data disks check already does.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Keep creating issues on supervised, only skip the Sentry report

Per review, failed host units can still be useful information for the
admin of a supervised system, so keep creating resolution issues there.
Only the Sentry report is limited to Home Assistant OS, there is nothing
we can do about units of a supervised installation.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-07-07 20:27:02 +02:00

check

Only report systemd unit failures to Sentry on Home Assistant OS (#7009 )

2026-07-07 20:27:02 +02:00

evaluation

Fix off-by-one in unsupported os_version evaluation (#6888 )

2026-05-28 12:47:27 +02:00

evaluations

Refine Docker timeout handling and add regression tests (#6970 )

2026-06-26 15:15:10 +02:00

fixup

Add unhealthy reasons for fsck failures and issues for other systemd failures (#6976 )