home-assistant
Unable to update from 2025.11.3 to 2025.12.1
The problem
I have tried to install the update using the GUI and the command line, both of them stating the update was finished succesfully but still 2025.11.3 is installed.
Steps I did:
- Rebooted HA and tried to install 2025.12.1 via the GUI
- Rebooted HA and tried to install 2025.12.1 via command line (core update --version 2025.12.1)
- Altered logger, logs, homeassistant.core to info and restarted. Fixed a few issues with a custom script and tried again with same result
- Checked free space (66% is free)
What can cause the issue and how to solve it?
What version of Home Assistant Core has the issue?
core-2025.12.1
What was the last working version of Home Assistant Core?
core-2025.11.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Unknown
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Running it on Synology within Virtual Machine Manager
This looks like an update or Supervisor/OS behavior rather than a bug in Home Assistant Core itself. Core issues on GitHub are generally for confirmed bugs in the core codebase.
If the update appears successful but the system stays on 2025.11.3, that usually means Supervisor rolled back the update due to a compatibility check or an error during boot. The Supervisor logs will show exactly why.
You’ll get more targeted help by posting this on the Home Assistant Community Forum or Discord, where people can walk through the logs with you.
If Supervisor logs indicate an OS-level update failure, the correct place to open an issue would be the home-assistant/supervisor or home-assistant/operating-system repository.
Strange since I did not add plugins or other code and the updates previously went fine.
I see a lot of warnings and a rollback in the Supervisor log:
[11:17:53] WARNING: Halt Supervisor [11:17:53] INFO: Supervisor restart after closing s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/udev.sh [11:24:31] INFO: Using udev information from host cont-init: info: /etc/cont-init.d/udev.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun supervisor (no readiness notification) services-up: info: copying legacy longrun watchdog (no readiness notification) s6-rc: info: service legacy-services successfully started [11:24:32] INFO: Starting local supervisor watchdog... 2025-12-07 11:24:42.850 INFO (MainThread) [__main__] Initializing Supervisor setup 2025-12-07 12:24:43.452 INFO (MainThread) [__main__] Setting up Supervisor 2025-12-07 12:24:44.812 WARNING (SyncWorker_1) [supervisor.host.sound] Can't update PulseAudio data: Failed to connect to pulseaudio server 2025-12-07 12:31:35.822 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Overseerr' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:35.918 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Folding@home' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:35.949 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Grocy' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:35.976 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'MQTT IO' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.023 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Nginx Proxy Manager' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.165 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Log Viewer' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.183 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Tailscale' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.272 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Traccar' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.334 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'Glances' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:31:36.375 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on 'InfluxDB' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-07 12:36:03.128 WARNING (MainThread) [supervisor.addons.addon] Add-on 15d21743_samba_backup is not running 2025-12-07 12:38:49.052 INFO (MainThread) [__main__] Running Supervisor 2025-12-07 12:57:00.177 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error 2025-12-07 12:57:00.178 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback! Exception ignored in: <http.client.HTTPResponse object at 0x7fa75a0be740> Traceback (most recent call last): File "/usr/local/lib/python3.13/http/client.py", line 432, in close super().close() # set "closed" flag File "/usr/local/lib/python3.13/http/client.py", line 445, in flush self.fp.flush() ValueError: I/O operation on closed file. 2025-12-07 13:45:51.429 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error 2025-12-07 13:45:51.429 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback! Exception ignored in: <http.client.HTTPResponse object at 0x7fa75a0a01f0> Traceback (most recent call last): File "/usr/local/lib/python3.13/http/client.py", line 432, in close super().close() # set "closed" flag File "/usr/local/lib/python3.13/http/client.py", line 445, in flush self.fp.flush() ValueError: I/O operation on closed file. 2025-12-08 03:39:01.743 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Overseerr' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.799 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Folding@home' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.805 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Grocy' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.815 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'MQTT IO' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.834 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Nginx Proxy Manager' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.888 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Log Viewer' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.895 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Tailscale' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.942 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Traccar' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:01.978 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'Glances' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 03:39:02.008 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on 'InfluxDB' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.150 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Overseerr' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.191 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Folding@home' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.199 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Grocy' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.214 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'MQTT IO' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.235 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Nginx Proxy Manager' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.321 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Log Viewer' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.330 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Tailscale' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.396 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Traccar' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.436 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'Glances' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 06:39:05.463 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on 'InfluxDB' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.085 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Overseerr' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.139 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Folding@home' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.145 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Grocy' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.153 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'MQTT IO' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.167 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Nginx Proxy Manager' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.213 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Log Viewer' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.219 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Tailscale' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.258 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Traccar' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.288 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'Glances' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 09:39:08.320 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on 'InfluxDB' uses deprecated 'codenotary' field in config. This field is no longer used and will be ignored. Please report this to the maintainer. 2025-12-08 12:19:54.512 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error 2025-12-08 12:19:54.514 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback! Exception ignored in: <http.client.HTTPResponse object at 0x7fa75a0bd450> Traceback (most recent call last): File "/usr/local/lib/python3.13/http/client.py", line 432, in close super().close() # set "closed" flag File "/usr/local/lib/python3.13/http/client.py", line 445, in flush self.fp.flush() ValueError: I/O operation on closed file. 2025-12-08 13:15:37.617 ERROR (MainThread) [supervisor.host.logs] Could not get a list of boot IDs from systemd-journal-gatewayd
Except for the warnings only a few lines are error or critical without stating what causes it? I've checked the other logs, no issues..
Based on the supervisor logs showing No Home Assistant Core response followed by a rollback, we can ascertain that the issue is a startup failure (or timeout) of the new Core version.
To find the root cause, we need to see the Core logs from the moment the update starts until Core either launches or fails. The Supervisor often overwrites these if the update fails quickly, so capturing them right away is important.
Please provide the output of: ha core logs
This will show if the problem is a critical error during startup or just a slow launch that timed out the Supervisor.
Same issue for me, I launch the update of core from 2025.11.3 to 2025.12.1 and always in 2025.11.3 after a process without any error message.
Something like this, starting at 2025-12-08 14:26:47? I disabled a few plugins (file editor, terminal)
2025-12-08 13:15:37.617 ERROR (MainThread) [supervisor.host.logs] Could not get a list of boot IDs from systemd-journal-gatewayd 2025-12-08 14:26:47.855 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error 2025-12-08 14:26:47.856 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback! Exception ignored in: <http.client.HTTPResponse object at 0x7fa75790c1c0> Traceback (most recent call last): File "/usr/local/lib/python3.13/http/client.py", line 432, in close super().close() # set "closed" flag File "/usr/local/lib/python3.13/http/client.py", line 445, in flush self.fp.flush() ValueError: I/O operation on closed file.
Those are the supervisor logs (They're showing that the Supervisor triggered a rollback because Core failed to respond in time, but they don't show why it hung. The ValueError is just a side effect of the connection closing)
If you look in the config folder, you might see a home-assistant.log.1. file, which should contain the logs from the failed session. This is where the actual error will be.
Also, given there is a systemd error there - When you mentioned "Rebooted HA", did you perform a full Host/System Reboot (Hardware/VM power cycle) or just a restart of the Home Assistant application?
Thanks, The log file only shows old logging of 2025-11-21? If I delete it and restart HA, will it be recreated?
'Rebooted HA' is that I chose the Reboot System option under System, Advanced Options (I assume this is a complete restart)
Yes, I think you can safely delete any log files and upon restart it will be recreated, which will provide a clean log of exactly what happens.
So
- Delete the home-assistant.log file.
- Try the update to 2025.12.1 again.
- If it reverts back to the old version, check the newly created home-assistant.log for errors.
And yes, System > Advanced Options > Reboot System is the correct way to perform a full host restart (which restarts the Supervisor and OS, not just the Core application).
Renamed the home-assistant.log.1 to home-assistant.log.1.old and installed 2025.12.1 via core update --version 2025.12.1. Still failed but also no home-assistant.log.1 created.
Did it create a 'home-assistant.log'? If so, we need the logs at the beginning of that one.
No, no home-assistant.log.1 was created after running the update. It doesn't have anything to do with the logger: value?
Restarted HA, restored previous home-assistant.log.1, change rights to 666 (rw/rw/rw instead of 644) and ran the update again. Let's see if anything happens now.
Still no changes to home-assistant.log.1, still dated 2025-11-21 :(
@angelgtc87 does your home-assistant.log.1 show any data, mine isn't generated when deleted or changed when available.
@angelgtc87 so also no home-assistant.log.1 change after latest updates dated today (last updates are for me 21-11, also to 2025.11.3)? I'm thinking to maybe rollback to 2025.11.2 and try to update from there
Apologies, I just spotted that the latest versions of supervised installation will no longer write the log files to disk: https://github.com/home-assistant/core/pull/146675.
This is why these log files are no longer updated.
With terminal access, try running this command immediately after the update fails and rolls back:
journalctl -t homeassistant --no-pager -n 100
I also have this issue. Have rebooted HA, VM, and Synology NAS that contains VM.
I can't determine what is causing the silent roll-back to 2025.11.3.
I used this command via the web SSH: ha core logs -n 5000 and filtered out some sensor logging
Add me to the list. HA running in VM on Synology NAS is failing and silently rolls back to HA Core 2025.11.3. This has happened with 2025.12.1 and 2025.12.2.
Changed VM priority to 'above normal' and updated to 2025.12.2. Eventually, after a long time, 2025.12.2 was installed!? Somehow the installation finished succesfully now without a clear fix.
My update finally succeeded, but only after a new update (2025.12.2) became available.