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

   I tried to manually update a Superset installation from 2.0.1 to 2.1.0 on a 
Ubuntu 20.04.6 LTS cloud instance.  It first gave a warning about pip to be 
updated.  With that I updated pip first and then apache-superset.  The update 
mentioned conflicts for pyopenssl and cryptography so I used pyopenssl 
cryptography==39.0.2.  However, the db upgrade step failed as it cannot connect 
to db although superset_config.py file is just working fine on 2.0.1.
   
   #### How to reproduce the bug
   
   1. pip install --upgrade pip
   2. pip install apache-superset --upgrade
   3. pip install pyopenssl cryptography==39.0.2
   4. superset db upgrade
   
   ### Expected results
   
   `superser db upgrade` command to succeed and db to be updated.
   
   ### Actual results
   
   `superser db upgrade` command fails with an error that it cannot connect to 
the database.  The log connection string seems to be wrong but it works as 
expected on 2.0.1.
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   
   ### Environment
   
   (please complete the following information):
   
   - Latest Chrome
   - superset version: 2.0,1
   - python version: 3.8.10
   - any feature flags active: 
       "ALERT_REPORTS": True,
       "DASHBOARD_NATIVE_FILTERS": True,
       "DASHBOARD_CROSS_FILTERS": True,
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   Add any other context about the problem here.
   


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