muthyas opened a new issue, #26976:
URL: https://github.com/apache/superset/issues/26976

   ### Bug description
   
   As we rolled out superset into production, we changed the database password. 
The same was changed in Superset Settings->Data Connections as well. However, 
none of the datasets are now loading as the schema loading fails. Also see in 
the logs that password authentication has failed. For some reason, although the 
password was changed in Superset reflecting new password, the datasets are 
failing to load the schema.  
   
   ### How to reproduce the bug
   
   Start new installation of Superset with psycopg2. . Add a Data Connection 
pointing to Postgres db. Load a new Dataset / table into superset.
   
   Next change the password in postgres DB. In Superset, click on 
Settings->Data Connections and edit the Database password to reflect the new 
password. Once database password is saved in Superset, go back and click on 
Data Connection. Database schema loading fails. 
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   3.1.0
   
   ### Python version
   
   3.10
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] 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.


-- 
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]

Reply via email to