[Urgent] Unable to load superset stuck in welcome page post login

Superset docker-compose deployment not proceeding after login. Returns 404 for /static/assets/images/loading.gif

How to reproduce the bug

1. Clone superset repo.
2. cd superset and use docker-compose up -d to bring up containers.
3. Open developer tools and log in to Superset with admin creds.
4. Post login it redirects to http://localhost:8088/superset/welcome/ and is stuck there

Expected results

Should Proceed to further screens.

Actual results

Page is stuck at http://localhost:8088/superset/welcome/ and in developer tools, under Network we can see http://localhost:8088/static/assets/images/loading.gif returning 404.

Screenshots

Environment

• browser type and version: Chrome - Version 94.0.4606.61 (Official Build) (64-bit)
• superset version: Observed in docker images on both apache/superset:latest-dev (sha256:a430759eb60d3dc1ddf905eb5b3afdeccdd17c8ece7370c71901ed1b68f5fbbb) and apache/superset:latest (sha256:f7afd84becc688f239228b2460910e316c1e140baf943115c3eca1be00ef6ccc)
• python version: 3.8.12 (python verso=ion found in apache/superset:latest-dev image)
• node.js version: node:16 (sha256:ed7bbdf4d76e3083f22827edc444b061b6562cb08341be973bfde0a972b65272)(docker image)
• any feature flags active: not sure. nothing has been changed in code/config post cloning.

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

I have cloned the repo and used docker-compose to bring up the system. I can also see that containers superset_worker_beat, superset_worker to be unhealthy.

Superset app logs

127.0.0.1 - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
2021-10-12 18:00:24,588:INFO:werkzeug:127.0.0.1 - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,596:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,791:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,818:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,894:WARNING:superset.views.base:404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
2021-10-12 18:00:25,895:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -

[maartenbreddels]

Docker didn’t work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:

# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

[jomach]

I had the same issue. Wait for 10 or 15 minutes then npm has installed all packages. This is imho a bug