Core: Update from 0.100.1 to 0.101.2 fails inexplicably

[Pe-MaKer]

Home Assistant release with the issue:

0.100.1

Last working Home Assistant release (if known):
0.100.1

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Integration:

Description of problem:
When I update Home Assistant to 0.101.2 via Hass.io Dashboard or via CLI the update process takes much longer then usual and even if the CLI "Command completed successfully", I'm still on v0.100.1.

core-ssh:~# hassio ha update
Processing... Done.
Command completed successfully

Looking at the logs and status info provided via CLI is not really helpful - at least for me:

core-ssh:/config# hassio homeassistant info
arch: armv7
boot: true
custom: false
image: homeassistant/raspberrypi3-homeassistant
ip_address: 172.30.32.1
last_version: 0.101.2
machine: raspberrypi3
port: 8123
ssl: true
version: 0.101.2
wait_boot: 600
watchdog: true

and some seconds later:

core-ssh:/config# hassio homeassistant info
arch: armv7
boot: true
custom: false
image: homeassistant/raspberrypi3-homeassistant
ip_address: 172.30.32.1
last_version: 0.101.2
machine: raspberrypi3
port: 8123
ssl: true
version: 0.100.1
wait_boot: 600
watchdog: true

It looks like the upgrade to 0.101.2 will be undone and the old version 0.100.1 would be restored.

core-ssh:/config# hassio homeassistant logs
2019-11-05 13:24:20 INFO (SyncWorker_0) [homeassistant.config] Upgrading configuration directory from 0.101.2 to 0.100.1
2019-11-05 13:24:23 INFO (SyncWorker_1) [homeassistant.loader] Loaded fritzbox_tools from custom_components.fritzbox_tools
2019-11-05 13:24:23 INFO (SyncWorker_10) [homeassistant.loader] Loaded hacs from custom_components.hacs
2019-11-05 13:24:23 INFO (SyncWorker_6) [homeassistant.loader] Loaded braviatv_psk from custom_components.braviatv_psk
2019-11-05 13:24:23 INFO (SyncWorker_5) [homeassistant.loader] Loaded circadian_lighting from custom_components.circadian_lighting
2019-11-05 13:24:23 INFO (SyncWorker_9) [homeassistant.loader] Loaded pmk-net.duckdns.org from custom_components.huesensor
2019-11-05 13:24:23 INFO (SyncWorker_1) [homeassistant.loader] Loaded air_quality from homeassistant.components.air_quality
2019-11-05 13:24:23 INFO (SyncWorker_11) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2019-11-05 13:24:23 INFO (SyncWorker_8) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2019-11-05 13:24:24 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for circadian_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-11-05 13:24:24 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for enigma which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-11-05 13:24:24 INFO (MainThread) [homeassistant.loader] Loaded enigma from custom_components.enigma
2019-11-05 13:24:24 INFO (SyncWorker_4) [homeassistant.util.package] Attempting install of beautifulsoup4==4.6.3
2019-11-05 13:25:08 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for fritzbox_tools which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-11-05 13:25:08 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of fritzconnection==0.8.4

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[frenck]

If Home Assistant fails to start, after upgrade, Hass.io will automatically downgrade to prevent you are ending up with a broken system.

Some tips:

• Check the homeassistant.log file, since it contains more history.
• Use the "Configuration Check" add-on, to check your current configuration against the latest version of Home Assistant (without changing your current running system). That add-on will return possible issues with your config in the add-on log.

[manuelbarbosa]

This is related with some changes that where made to Home Assistant, to update follow this steps:

• rename configuration.yaml -> configuration.yaml.bkp
• create a new configuration.yaml with only one line default_config:
• restart home assistant so it will load this config
• update home assistant to the new version
• after the upgrade completes, delete the configuration.yaml
• rename configuration.yaml.bkp -> configuration.yaml
• valide the old config before rebooting and fix the necessary erros:
• 
  
  • the ones I had to resolve where remove the legacy password from http module and trusted networks
  
  
• after the config passes the validation check, you can safely restart hass.io

Hope this helps

[tiagofreire-pt]

This is related with some changes that where made to Home Assistant, to update follow this steps:

* rename `configuration.yaml` -> `configuration.yaml.bkp`

* create a new configuration.yaml with only one line `default_config:`

* restart home assistant so it will load this config

* update home assistant to the new version

* after the upgrade completes, delete the `configuration.yaml`

* rename `configuration.yaml.bkp` -> `configuration.yaml`

* valide the old config before rebooting and fix the necessary erros:

* * the ones I had to resolve where remove the legacy password from http module and trusted networks

* after the config passes the validation check, you can safely restart hass.io

Hope this helps

Is this solved on version 0.101.3?

Thanks.

[manuelbarbosa]

No, I did the upgrade from 0.100 to 0.101.3 and faced the same issue

[Pe-MaKer]

Hey, @frenck ,
I'm honored that it is you of all people who answer me. Thanks for your work in the development and distribution of Home Assistant, your contributions on Github and of course your Youtube videos. You have helped me a lot with all this.

To my problem:
As usual I took a snapshot and checked with the "Configuration Check" if I can do the update without problems. The plugin took almost half an hour ( usually only a few minutes) and instead of displaying the message "Configuration check finished - no error found" the addon simply terminated. Maybe by a timeout? In any case without error or approval.
So I just tried the update.

After I found no fatal error in home-assistant.log, I add the relevant section.
Maybe you can identify the reason of the error here.
home-assistant.log
The log starts shortly before I started the update to 0.101.2 in the UI and ends shortly after the web frontend was reachable again.

@manuelbarbosa thanks mate!
I followed your steps and that did the trick. The only change I had to make was getting rid of the legacy password.

[frenck]

@Pe-MaKer The error that is causing the culprit is in that log file you've provided.

2019-11-06 12:56:18 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: [api_password] is an invalid option for [http]. Check: http->http->api_password. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/http/

This has been removed and noted as a breaking change in the release notes.

And PS: Thank you for the kind words, sir!

[frenck]

Since it all got resolved 🎉 I'll go ahead and close up this issue.