Update from 2021.1.4 to 2021.1.5 failed

[Pirol62]

The problem

Update from 2021.1.4 to 5 failed.
Result:

• The connect to cloud was not possible. (System not available)
• All sensors to the OS (CPU,SWAP etx) were unavailable.
• Places Component was unavailable
• Browser_mod could not be installed
• A restart wasn’t possible. Click on restart was simply ignored.

Now, after the rollback to 2021.1.4, everything’s working again.
What can I do now? What went wrong?

Environment

System Health

version	2021.1.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.8.7
os_name	Linux
os_version	4.19.93-v7
arch	armv7l
timezone	Europe/Berlin

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	4907
Installed Version	1.10.1
Stage	running
Available Repositories	713
Installed Repositories	31

Home Assistant Cloud

logged_in	true
subscription_expiration	29. Januar 2021, 1:00
relayer_connected	true
remote_enabled	false
remote_connected	true
alexa_enabled	true
google_enabled	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Hass.io

host_os	HassOS 3.11
update_channel	stable
supervisor_version	2021.01.7
docker_version	19.03.5
disk_total	28.6 GB
disk_used	3.0 GB
healthy	true
supported	true
board	rpi3
supervisor_api	ok
version_api	ok
installed_addons	Samba share (9.3.0), Duck DNS (1.12.4), deCONZ (5.3.4), File editor (5.2.0), SQLite Web (2.3.2), Dropbox Sync (1.3.0), Check Home Assistant configuration (3.6.0)

Lovelace

dashboards	6
mode	storage
views	11
resources	17

• Home Assistant Core release with the issue:
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core):
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Copy to clipboard
Logger: homeassistant.components.hassio.http
Source: components/hassio/http.py:126
Integration: Hass.io (documentation, issues)
First occurred: 13:07:03 (5 occurrences)
Last logged: 13:07:06

Client error on api snapshots/reload request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
Client error on api supervisor/logs request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
Client error on api network/info request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
Client error on api supervisor/stats request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]
Client error on api core/stats request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]

Additional information

[frenck]

Hmm weird. Anything related in e.g., the supervisor logs?

[Pirol62]

No, the supervior logs where "green".(I just watched the color ) .
There is another guy facing problems after the update:
https://community.home-assistant.io/t/browser-mod-turn-your-browser-into-a-controllable-device-and-a-media-player/123806/941?u=pirol62

The really strange thing is, that the restart button was ignored. Maybe some or more restarts might fixed it, but it wasn't possible, neither from supervisor/system nor via configuration/manage server

PS: I remember, that after the first look into subervisor, the version was 2021.01.5
Then, after some minutes, the version changed to 2021.01.7, obviously the update of the supervisor followed the core.
But that didn't change the overall situation.

[frenck]

The link you gave is about a custom component, which we do not support.

hen, after some minutes, the version changed to 2021.01.7

That is unrelated, the Supervisor auto-updates and should not affect the Core.

[26tajeen]

I am "the other guy". I just wondered if it's occasionally necessary to do a couple of reboots after upgrading to a new version of Home Assistant before things 'settle' ?
Unusually when I upgraded my instance I began getting messages from Home Assistant via Telegram to say it had restarted, but then it 'froze', the front end was not accessible and I feared the worst.
Happily, however, I was able to login via SSH and restore a snapshot.

[Pirol62]

I am "the other guy".

sorry ;-) You're right. It sounds a little unfriendly.
That wasn't my intention.

[26tajeen]

haha! :-D
I actually hadn't taken offence nor did I think it rude.
No problem at all.

[Pirol62]

Hi @frenck ,
2021.2.0 is in sight.
The security update is still waiting.

Are there any ideas, what happend?
Are there maybe some fixes regarding this?

[26tajeen]

This is a major issue, just had a related problem with an entirely separate HA instance at another location on other hardware. My system is currently hosed due to this ridiculous 404 Client Error for http+docker

[Pirol62]

Hi, as I would like to update to from 2021.1.3 to 2021.3.4 I'm wondering if there is something happened on this issue.
Can I simply try to update anyway? I'd like to avoid heavy trouble because I have a lot to do at work and therefor not that much time to tinker out configurations.
The HA configuration checker has been executed and did not detect issues

[Pirol62]

Ok, already updated successfully to 2021.3.4.
The issue must have been temporarily.
I close this thread.