The deploy reporting to uat build is currently failing. Because of it, it's impossible to go to any of the Superset reports on either browser. Please look at the attached screenshots.
Log into the application as administrator.
Go to Administration > Reports.
Choose any Superset report.
One doesn't go to the report. Instead, errors in the console and on the UI occur.
The deploy reporting to uat build has to be passing;
It should be possible to access Superset reports.
Thank you! I started testing the ticket and see that the build has been passing each time for some time. But I noticed one possible issue: Even though the master node is empty, the Deploy reporting to uat build hasn't started but it's in the build queue. It's been waiting for 18 minutes now, and it was triggered by the previous deploy to UAT (I managed to re-deploy UAT for the second time since then). Please look at the screenshot.
EDIT: I finished testing the ticket and still, the deploy reporting to uat build didn't start, as on the screenshot. It's probably frozen, and I don't have necessary permissions to kill it. I also am able to access Superset reports now but the only one that contains any data is the Administrative one. It's possible that something's wrong with NiFi because I see that there are active threads but 0 bytes transferred in the processor groups. Please let me know what you think.
If you hover over the build it tells you the reason it doesn’t run yet - it’s set to not deploy more frequently than every 2 hours.
OK, I see. The re-deploys (regular and of reporting) to UAT have just finished, so I'll check what it looks like now.
I checked again, and now there are data in the reports. Also, the NiFi flows work as they should. I'll move the ticket to Done then.