Stefan Agner 1e49129197

Use longer timeouts for API checks before trigger a rollback (#4658) ...

* Don't check if Core is running to trigger rollback

Currently we check for Core API access and that the state is running. If
this is not fulfilled within 5 minutes, we rollback to the previous
version.

It can take quite a while until Home Assistant Core is in state running.
In fact, after going through bootstrap, it can theoretically take
indefinitely (as in there is no timeout from Core side).

So to trigger rollback, rather than check the state to be running, just
check if the API is accessible in this case. This prevents spurious
rollbacks.

* Check Core status with and timeout after a longer time

Instead of checking the Core API just for response, do check the
state. Use a timeout which is long enough to cover all stages and
other timeouts during Core startup.

* Introduce get_api_state and better status messages

* Update supervisor/homeassistant/api.py

Co-authored-by: J. Nick Koston <nick@koston.org>

* Add successful start test

---------

Co-authored-by: J. Nick Koston <nick@koston.org>

2023-11-01 16:01:38 -04:00

..

test_core.py

Use longer timeouts for API checks before trigger a rollback (#4658)

2023-11-01 16:01:38 -04:00

test_home_assistant_watchdog.py

Reduce executor code for docker (#4438)

2023-07-18 11:39:39 -04:00

test_module.py

Handle get users API returning None (#4628)

2023-10-16 21:54:50 +02:00

test_websocket.py

Separate startup event from update check event (#4425)

2023-07-06 12:45:37 -04:00