superset k8s deployment via helm

[sainikhilsamineni]

@dosu i have deployed superset on an eks via helm with internal cache and external rds. it wS working fine and suddenly after few days after login page it is showing 500 error. reasons ?

[dosubot[bot]]

A 500 error after login in Superset on EKS via Helm with internal cache and external RDS is almost always due to a failure in either the cache or database layer, or a misconfiguration that impacts session or bootstrap data loading. The most common causes are:

• Loss of connectivity to your RDS instance (check DB credentials, network policies, or RDS health).
• Cache backend issues: if Redis (or your cache) is unavailable or misconfigured, Superset may fall back to using the metadata DB for cache, making DB connectivity even more critical. Some users have reported that using AWS Elasticache for Redis caused similar issues, and switching to the Redis Helm chart resolved it (source).
• Configuration drift: changes in secrets, environment variables, or Helm values (especially SECRET_KEY, DB credentials, or cache config) can break authentication/session handling and cause 500s (source).
• Missing dependencies: if your bootstrap script or image is missing required Python packages (like psycopg2-binary for PostgreSQL), you can get runtime errors (source).
• Readiness/liveness probe failures or pod restarts can disrupt service and trigger 500s.

To troubleshoot:

1. Check Superset pod logs right after reproducing the error (kubectl logs <pod>) for stack traces or DB/cache errors.
2. Validate RDS connectivity from your pods (network, credentials, DB health).
3. Validate cache backend connectivity and configuration.
4. Check for recent changes in Helm values, secrets, or environment variables.
5. Make sure your SECRET_KEY is unique and not the default.

If you can share the relevant log lines from the time of the 500 error, it will help pinpoint the root cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[sainikhilsamineni]

@dosu 10.190.110.26 - - [17/Dec/2025:05:09:30 +0000] "GET /health HTTP/1.1" 200 2 "-" "kube-probe/1.33+"
10.190.3.27 - - [17/Dec/2025:05:09:35 +0000] "GET /health HTTP/1.1" 200 2 "-" "ELB-HealthChecker/2.0"
2025-12-17 05:09:39,490:WARNING:superset.views.error_handling:Exception
Traceback (most recent call last):
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/base.py", line 1694, in _entity_namespace_key
return getattr(ns, key)
AttributeError: type object 'Role' has no attribute 'username'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
rv = self.dispatch_request()
File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/app/superset/multi_tenant.py", line 180, in login_with_tenant
return super().login()
File "/app/.venv/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 36, in wrapped_view
response = make_response(view(*args, **kwargs))
File "/app/.venv/lib/python3.10/site-packages/flask_appbuilder/security/views.py", line 530, in login
user = self.appbuilder.sm.auth_user_db(
File "/app/superset/multi_tenant.py", line 351, in auth_user_db
user = self.get_session.query(self.user_model).filter_by(
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 1806, in filter_by
clauses = [
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 1807, in
entity_namespace_key(from_entity, key) == value
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/base.py", line 1696, in entity_namespace_key
util.raise(
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise
raise exception
sqlalchemy.exc.InvalidRequestError: Entity namespace for "mapped class Role->ab_role" has no property "username"
2025-12-17 05:09:39,491:ERROR:superset.views.error_handling:Entity namespace for "mapped class Role->ab_role" has no property "username"
Traceback (most recent call last):
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/base.py", line 1694, in _entity_namespace_key
return getattr(ns, key)
AttributeError: type object 'Role' has no attribute 'username'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
rv = self.dispatch_request()
File "/app/.venv/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/app/superset/multi_tenant.py", line 180, in login_with_tenant
return super().login()
File "/app/.venv/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 36, in wrapped_view
response = make_response(view(*args, **kwargs))
File "/app/.venv/lib/python3.10/site-packages/flask_appbuilder/security/views.py", line 530, in login
user = self.appbuilder.sm.auth_user_db(
File "/app/superset/multi_tenant.py", line 351, in auth_user_db
user = self.get_session.query(self.user_model).filter_by(
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 1806, in filter_by
clauses = [
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 1807, in
entity_namespace_key(from_entity, key) == value
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/base.py", line 1696, in entity_namespace_key
util.raise(
File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise
raise exception
sqlalchemy.exc.InvalidRequestError: Entity namespace for "mapped class Role->ab_role" has no property "username"
Login attempt for tenant: HXGNDEV0025_AX1
Authenticating user: [email protected] with tenantid from request
Tenant ID from request: HXGNDEV0025_AX1
10.190.2.100 - - [17/Dec/2025:05:09:39 +0000] "POST /login?tenant=HXGNDEV0025_AX1 HTTP/1.1" 500 0 "https://superset.pcrt.stg.hxgnsmartcloud.com/login?tenant=HXGNDEV0025_AX1" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
10.190.2.100 - - [17/Dec/2025:05:09:39 +0000] "GET /static/assets/b01fb73b111d937e4c09.png HTTP/1.1" 200 0 "https://superset.pcrt.stg.hxgnsmartcloud.com/login?tenant=HXGNDEV0025_AX1" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
10.190.2.100 - - [17/Dec/2025:05:09:40 +0000] "GET /static/assets/e3bafb62eb2592c0bb0e.png HTTP/1.1" 200 0 "https://superset.pcrt.stg.hxgnsmartcloud.com/login?tenant=HXGNDEV0025_AX1" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
10.190.1.109 - - [17/Dec/2025:05:09:40 +0000] "GET /health HTTP/1.1"

[dosubot[bot]]

The error is happening because your custom multi-tenant authentication code is trying to filter the Role model by username, but the Role model in Superset (and Flask AppBuilder) does not have a username property—only the User model does. This usually means that somewhere in your custom code (likely in /app/superset/multi_tenant.py), self.user_model is set to Role instead of User, or a query is being run against Role when it should be against User.

To fix this, review your authentication logic and make sure any query filtering by username is performed on the User model, not Role. For reference, you can look at Superset’s standard authentication and security manager code in superset/security/manager.py for the correct patterns. This is a common pitfall in custom multi-tenant setups and is not part of standard Superset behavior. More details and examples are discussed here.

If you need a code example or further guidance, let me know!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}