GitHub user SB-MFJ added a comment to the discussion: Need help setting up Superset chart in AWS EKS behind ALB
Noticed this error: ``` superset-init-db 2025-12-03 16:35:54,905:INFO:superset.security.manager:Syncing role definition superset-init-db 2025-12-03 16:35:54,959:INFO:superset.security.manager:Syncing Admin perms superset-init-db 2025-12-03 16:35:54,965:INFO:superset.security.manager:Syncing Alpha perms superset-init-db 2025-12-03 16:35:54,971:INFO:superset.security.manager:Syncing Gamma perms superset-init-db 2025-12-03 16:35:54,978:INFO:superset.security.manager:Syncing sql_lab perms superset-init-db 2025-12-03 16:35:54,983:INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing superset-init-db 2025-12-03 16:35:54,987:INFO:superset.security.manager:Creating missing datasource permissions. superset-init-db 2025-12-03 16:35:54,992:INFO:superset.security.manager:Creating missing database permissions. superset-init-db 2025-12-03 16:35:54,995:INFO:superset.security.manager:Cleaning faulty perms superset-init-db Creating admin user... superset-init-db Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py] superset-init-db 2025-12-03 16:35:59,525:DEBUG:superset.utils.logging_configurator:logging was configured successfully superset-init-db 2025-12-03 16:35:59,588:DEBUG:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'> superset-init-db 2025-12-03 16:35:59,599:DEBUG:superset.initialization:Setting database isolation level to READ COMMITTED superset-init-db /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:324: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. superset-init-db warnings.warn( superset-init-db 2025-12-03 16:36:00,168:INFO:alembic.runtime.migration:Context impl PostgresqlImpl. superset-init-db 2025-12-03 16:36:00,168:INFO:alembic.runtime.migration:Will assume transactional DDL. superset-init-db 2025-12-03 16:36:00,409:INFO:superset.app:Syncing configuration to database... superset-init-db 2025-12-03 16:36:00,417:DEBUG:superset.commands.theme.seed:Updated system theme: THEME_DEFAULT superset-init-db 2025-12-03 16:36:00,422:DEBUG:superset.commands.theme.seed:Updated system theme: THEME_DARK superset-init-db 2025-12-03 16:36:00,424:INFO:superset.app:Configuration sync to database completed successfully superset-init-db Recognized LDAP Authentication. superset-init-db Error! User already exists supersetadmin ``` this user is created by the app with the helm values: init.adminUser.username init.adminUser.password The database is blank, so I'm not sure where this error is coming from are there steps beyond that are failing to execute that may cause the werkzeug error? GitHub link: https://github.com/apache/superset/discussions/36296#discussioncomment-15151890 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
