App stuck in error when editing location (domain) while app is shut down

[Valexico]

Hi

I had an issue last week with an application (Baserow) :

• The app was stopped
• I tried to add a domain alias in "location" setting

After that the app was stuck in Error state, with error Error : Inactive - Error getting IP of redis-184ad096-6567-4511-b1a6-b40814b54793 service.

I tried everything but couldn't restart the app. I had to install a new baserow instance and restore from a backup, delete the old one and change the domain again while the app was running.

Today I did a new test to confirm the bug, even with a simple app (LAMP server). And I could reproduce 100% :

• Install LAMP
• Stop App
• Add a domain alias
• -> App stuck in Error mode Error : Inactive - Error getting IP of redis-184ad096-6567-4511-b1a6-b40814b54793 service

Is there a technique to reboot such stopped App ? I could be very dangerous in production ?

And maybe this issue could be adressed ?

Cheers

[nebulon]

Thanks for the report, I can easily reproduce this.

The issue is, that stopping the app also stops the redis container with it. However adding an alias triggers an internal app task, which depends on this redis container to be reachable (this is probably the bug).

We will fix it for next version. If you hit this, just manually start the redis container in the services view.

[Valexico]

Thanks for the details

[jdaviescoates]

@Valexico just to be sure: you do realise that you don't need to stop apps before editing/ adding locations, right? (which is I guess why no one previously spotted this behaviour)

[Valexico]

Yes, it was not on purpose. Nonetheless current behaviour is dangerous if you don't know the technique to restart your stucked app