Bug description
I'm coming from 4.1.3. When I deployed 6.0.0rc1 to my test environment and try to visit the application I get:
superset_app | 172.31.13.11:61783 - - [05/Sep/2025:18:40:37 +0000] "GET /superset/welcome/ HTTP/1.1" 302 201 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0"
superset_app | 2025-09-05 18:40:37,859:WARNING:superset.views.error_handling:Exception
superset_app | Traceback (most recent call last):
superset_app | File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context
superset_app | self.dialect.do_execute(
superset_app | File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
superset_app | cursor.execute(statement, parameters)
superset_app | psycopg2.errors.UndefinedTable: relation "themes" does not exist
superset_app | LINE 2: FROM themes
I notice there was a migration failure, I wonder if this is related:
superset_init | 2025-09-05 18:38:11,777:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "pg_type_typname_nsp_index"
superset_init | DETAIL: Key (typname, typnamespace)=(ab_group_id_seq, 2200) already exists.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
I don't know
Browser
Firefox
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: sfirke
Oops I see this is a duplicate of https://github.com/apache/superset/issues/34403. I'll test rc2 when it comes out without this bug!