royspeedy commented on issue #42123: URL: https://github.com/apache/superset/issues/42123#issuecomment-5010266285
@dosu Update / clarification: I believe this is primarily a Superset-side error classification issue rather than a PostgreSQL connectivity problem. Evidence: - `get_sqla_engine()` works in `superset shell`. - `get_raw_connection(..., source=QuerySource.SQL_LAB)` also works in `superset shell`. - PostgreSQL server logs show no connection attempt when SQL Lab fails. - `allow_run_async = False`, so this is not the async worker path. This suggests the failure is being raised or reclassified inside Superset/FAB before the target database is reached. The current message "invalid username-password pair or user is disabled" is misleading because it does not distinguish metadata/auth/session problems from target DB authentication failures. Environment note: - Superset deployed via Helm on Kubernetes - Custom image: `my-superset:latest` - Custom `CUSTOM_SECURITY_MANAGER` was tested and removed, but the issue persisted - `RESULTS_BACKEND` is configured - No Celery worker pod is present - Superset version: 6.1.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
