Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Login not working AWS ECS #20101

Closed
M3gar00 opened this issue May 17, 2022 · 1 comment
Closed

Default Login not working AWS ECS #20101

M3gar00 opened this issue May 17, 2022 · 1 comment
Labels
#bug Bug report

Comments

@M3gar00
Copy link

M3gar00 commented May 17, 2022

I have used terraform to deploy Superset to ECS. In order to test baseline performance and connectivity, I left the username and password as the default: admin/admin.
The Dockerfile I'm using looks like:

FROM apache/superset
# Switching to root to install the required packages
USER root
# install trino so the Superset doesn't complain about it not being there
RUN pip install trino
USER superset
ENV SUPERSET_ENV dev

How to reproduce the bug

  1. Go to superset.myDomain.com
  2. enter admin for username
  3. enter admin for password

Expected results

Ability to login

Actual results

Invalid login. Please try again.

Environment

  • browser type and version: Chrome 101.0.4951.64
  • superset version: superset docker image:latest, digest: a8b3631068a6

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • [ X] 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

I have looked at similar issues that are addressed in non AWS ECS environments and have tried solutions presented in issue 10547 and issue 10149. The solutions presented there have not born fruit in this environment.

@M3gar00 M3gar00 added the #bug Bug report label May 17, 2022
@M3gar00
Copy link
Author

M3gar00 commented May 18, 2022

Further digging, it looks like the database is not initialized when the Docker container runs. I'm getting the error:

root:(sqlite3.OperationalError) no such table: logs

Still attempting to see why the database is not getting created.

@M3gar00 M3gar00 closed this as completed May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant