Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to update Core 2023.9.3 to 2023.10.5 #102993

Closed
Stefan28L opened this issue Oct 29, 2023 · 6 comments
Closed

Unable to update Core 2023.9.3 to 2023.10.5 #102993

Stefan28L opened this issue Oct 29, 2023 · 6 comments

Comments

@Stefan28L
Copy link

The problem

Try to update core to2023.10.5 on a RPi 3B+

Home Assistant 2023.9.3
Supervisor 2023.10.1
Operating System 11.1
Frontend 20230911.0 - latest

After update the HA boots two times, falling back to core 2023.9.3 again.

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

core-2023.9.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

Supervisor log:

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
[08:34:04] 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
[08:34:04] INFO: Starting local supervisor watchdog...
23-10-29 08:34:11 INFO (MainThread) [main] Initializing Supervisor setup
23-10-29 08:34:11 INFO (MainThread) [supervisor.utils.sentry] Initializing Supervisor Sentry
23-10-29 09:34:12 INFO (MainThread) [main] Setting up Supervisor
23-10-29 09:34:13 WARNING (SyncWorker_0) [supervisor.host.sound] Can't update PulseAudio data: Failed to connect to pulseaudio server
23-10-29 09:34:21 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:34:23 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:34:24 INFO (MainThread) [main] Running Supervisor
23-10-29 09:36:22 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:36:23 WARNING (SyncWorker_4) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling

23-10-29 09:39:41 WARNING (SyncWorker_0) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:39:42 WARNING (SyncWorker_7) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling

23-10-29 09:44:13 ERROR (MainThread) [supervisor.homeassistant.core] No API response in 5 minutes, assuming core has had a fatal startup error
23-10-29 09:44:13 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!

23-10-29 09:44:57 WARNING (SyncWorker_4) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:44:58 WARNING (SyncWorker_6) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling

23-10-29 09:49:29 ERROR (MainThread) [supervisor.homeassistant.core] No API response in 5 minutes, assuming core has had a fatal startup error

23-10-29 09:55:51 WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
23-10-29 09:55:52 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I think it doesn't depend on which version you update from. There are several similar bug reports online. For example from 2023.10.3 to 2023.10.5.

@home-assistant
Copy link

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of hassio can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


hassio documentation
hassio source
(message by IssueLinks)

@Ninuss
Copy link

Ninuss commented Oct 30, 2023

Same here from Home Assistant 2023.10.1 to 2023.10.5

@LinuxfarmerHH
Copy link

Here an update from 2023.10.3 to 2023.10.5 bombed hassio into pieces. System services does not start anymore, no automations, hailed with error codes. Hope a restore of 2023.10.3 is able to fix that situation.

@mstu01
Copy link

mstu01 commented Oct 31, 2023

I experienced the same problem, my instance wouldn't boot after the update from 2023.9.3 to2023.10.5. After installing the Supervisor Update first, everything works perfectly, maybe it also was because i removed the psu and attached it back after a few minutes.

@joostlek
Copy link
Member

Here an update from 2023.10.3 to 2023.10.5 bombed hassio into pieces. System services does not start anymore, no automations, hailed with error codes. Hope a restore of 2023.10.3 is able to fix that situation.

Please create a new issue and share logs, I think I might have an idea what causes this

@agners
Copy link
Member

agners commented Oct 31, 2023

23-10-29 09:44:13 ERROR (MainThread) [supervisor.homeassistant.core] No API response in 5 minutes, assuming core has had a fatal startup error

It seems that the current logic is too impatient for some setups. The issue is tracked in the Supervisor repository at home-assistant/supervisor#4655.

@agners agners closed this as completed Nov 6, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants