Upgrade to V0.40.0 from V0.38.1 starts at setup screen (ELB)

We are currently running V0.38.1 on ELB, I have performed upgrade as per instructions in https://www.metabase.com/docs/latest/operations-guide/upgrading-metabase.html
but when update is complete the environment starts at setup, all user data is gone. Not sure why as it points to the same database. I have rolled back to V0.38.1 and all is fine I can still access user data and dashboards etc

Hi @ChristineChetty
You need to decouple your RDS from EB:
https://www.metabase.com/docs/latest/operations-guide/creating-RDS-database-on-AWS.html#decouple-your-rds-database-from-the-elastic-beanstalk-deployment

Okay awesome will do this. Should probably include this step in the docs**

Just to be sure that we are on the same page, my database is currently in RDS (Postgres) so is already decoupled in that sense. Would I still need to do anything extra? I haven't had to delete an entire environment in the past in order to do an upgrade so just wondering why it's necessary now

@ChristineChetty If you never manually created the RDS before creating the EB, then it was created together (meaning it was coupled).
The entire EB script has been changed in 0.40.0

@ChristineChetty check out https://www.metabase.com/docs/latest/operations-guide/creating-RDS-database-on-AWS.html#decouple-your-rds-database-from-the-elastic-beanstalk-deployment

regards

AWS has since released feature to decouple database from the deployment like such: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.db.html#using-features.decoupling.db

I want to understand if I can simply decouple in this manner then upgrade my elastic beanstalk deployment then couple again?

Christine, coupling components is always bad. Your database should be decoupled from the application server always so those 2 components can be managed separately. Decouple with any mean you find easier and upgrade to b 41.4 ASAP

1 Like