Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Met with empty schemas page after docker-compose upgrade #3426

Closed
pavish opened this issue Jan 29, 2024 · 2 comments · Fixed by #3431
Closed

Met with empty schemas page after docker-compose upgrade #3426

pavish opened this issue Jan 29, 2024 · 2 comments · Fixed by #3431
Assignees
Labels
needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action priority: urgent Blocks other ongoing work restricted: maintainers Only maintainers can resolve this issue type: bug Something isn't working work: backend Related to Python, Django, and simple SQL
Milestone

Comments

@pavish
Copy link
Member

pavish commented Jan 29, 2024

Description

  • Performed a guided install of 0.1.3
    • It connects a single external user DB with 2 schemas and multiple tables.
  • Upgraded to 0.1.4 following the information in the latest docs (from Update Installation Documentation for Release 0.1.4 #3227).
    • Moved Postgres volumes as mentioned in docs.
  • Upgrade succeeded.
  • Met with the following page:
    Screenshot 2024-01-29 at 7 17 17 PM
  • I repeated the upgrade twice and this happened both times.
  • The database name, host, and port of the user database connection were empty.
    Screenshot 2024-01-29 at 7 18 48 PM
@pavish pavish added type: bug Something isn't working work: backend Related to Python, Django, and simple SQL restricted: maintainers Only maintainers can resolve this issue priority: urgent Blocks other ongoing work needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action labels Jan 29, 2024
@pavish pavish added this to the v0.1.4 milestone Jan 29, 2024
@mathemancer
Copy link
Contributor

@pavish Can you give me a little detail about whether you started with MATHESAR_DATABASES (I assume yes), whether you removed it, and when you removed it?

@pavish
Copy link
Member Author

pavish commented Jan 29, 2024

@mathemancer I did not remove it.

  • I followed the guided install script which installed Mathesar and set up the MATHESAR_DATABASES env variable.
    • I chose 'use existing' instead of 'create new' in the guided install DB prompt, and gave the credentials to an existing database.
  • I started Mathesar, it worked fine.
  • I then following the upgrade instructions as per the docs, and met with this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action priority: urgent Blocks other ongoing work restricted: maintainers Only maintainers can resolve this issue type: bug Something isn't working work: backend Related to Python, Django, and simple SQL
Projects
None yet
2 participants