SQLLab : error while fetching database list (0.36.0)(0.35.2)

Expected results

In SQLLab, list of databases is displayed and available

Actual results

No databases available, Toaster message “Error while fetching database list”

In browser console, there’s a 404

sqllab.2cb609d23e6326ebb8f8.entry.js:2 GET https://superset.mycompany.com/api/v1/database/?q=(keys:!(none),filters:!((col:expose_in_sqllab,opr:eq,value:!t)),order_columns:database_name,order_direction:asc,page:0,page_size:-1)

Screenshots

How to reproduce the bug

1. Login,
2. Click on SQL Lab
3. See error

Environment

(please complete the following information):

• superset version: 0.36.0
• python version: Python 3.6.10 :
• node.js version: v12.16.3
• npm version: 6.14.4

Checklist

Make sure these boxes are checked 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.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven’t found one similar.

Additional context

Running inside Docker, built on 0.36.0 tag sources

Using OAuth2

Migrating data from 0.34.0 with some errors

ERROR:superset.views.base:invalid literal for int() with base 10: 'Infinity'
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/superset/views/base.py", line 107, in wraps
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/flask_appbuilder/security/decorators.py", line 151, in wraps
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/superset/views/core.py", line 1055, in schemas
    db_id = int(db_id)
ValueError: invalid literal for int() with base 10: 'Infinity'

Note that creating a new database connexion does not solve anything.

[valferon]

I had the same issue and could see some missing dependencies in an exception in the logs. Had to add thrift / sasl dependencies in the docker image.

[elaademiir]

Sure, it all depends what you have in front of your superset installation. (could be apache, nginx, whatever). In my case I have a load balancer that makes some magic on hosts and urls to redirect queries to a given server. (shared resources for my test setup)

/api/v1 uri’s were redirected to another service. => superset never received them => superset front never got answers

I had to reorder priorities as they should always have been : if host = superset => all queries go to superset server.

this is the same error in my local superset venv. Sorry I couldnt understand the solution exactly. Can you please describe it more detail?