You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/08/13 10:31:19 UTC
[GitHub] [superset] crucialfelix opened a new issue #16247: docker-compose non-dev superset-init fails to migrate database
crucialfelix opened a new issue #16247:
URL: https://github.com/apache/superset/issues/16247
Following the documentation:
```
docker-compose -f docker-compose-non-dev.yml up
```
### Expected results
it should initialize and startup.
### Actual results
superset_init fails due to a missing table.
```
superset_init | sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation "ab_permission_view_role" does not exist
superset_init | LINE 2: FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_...
superset_init | ^
superset_init |
superset_init | [SQL: SELECT ab_role.id AS ab_role_id, ab_role.name AS ab_role_name, ab_permission_view_1.id AS ab_permission_view_1_id, ab_permission_view_1.permission_id AS ab_permission_view_1_permission_id, ab_permission_view_1.view_menu_id AS ab_permission_view_1_view_menu_id
superset_init | FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_permission_view_role_1 JOIN ab_permission_view AS ab_permission_view_1 ON ab_permission_view_1.id = ab_permission_view_role_1.permission_view_id) ON ab_role.id = ab_permission_view_role_1.role_id]
```
#### How to reproduce the bug
docker-compose -f docker-compose-non-dev.yml up
### Environment
- superset version: `superset version`
I tried both:
Today's master: d6f9c48aa1ed3f02f1d97f8fe3447798d2414544
tag: v2021.31.0 which looks like it was the last release
Though I guess in both cases it is only using the docker-compose file. Its the image that it's loading that is not working.
I also tried changing the docker-compose to point at master-dev rather than latest-dev:
x-superset-image: &superset-image apache/superset:master-dev
and
x-superset-image: &superset-image apache/superset:latest
### 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
Thanks, the project looks very interesting!
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] wengzhenjie commented on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
wengzhenjie commented on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-915692760
I have a same problem.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] vialcollet commented on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
vialcollet commented on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-900232116
Same issue 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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] wengzhenjie commented on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
wengzhenjie commented on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-915695008
> I have a same problem.
> 
I run this cmd `docker-compose down -v `. And then I run `docker-compose -f docker-compose-non-dev.yml up -d`. It works.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] crucialfelix commented on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
crucialfelix commented on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-925637079
I did get it to initialize by running:
```
docker-compose up superset-init
```
Let it finish initializing, then you can bring up the whole "cluster"
I think it can be fixed by changing the other services from:
depends_on: *superset-depends-on
to:
depends_on: superset-init
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] clorichel commented on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
clorichel commented on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-954579134
Watch out, the `depends_on` sounds like an appealing idea, but won't do it here because: _"for startup Compose does not wait until a container is “ready” (whatever that means for your particular application) - only until it’s running"_ as mentioned in the Docker documentation (https://docs.docker.com/compose/startup-order/).
So the other containers will actually start as soon as `superset-init` is _started_, not once it's _done_ doing all the stuff it's made to do.
Also been hitting this issue, and similarly to https://github.com/apache/superset/issues/10711 be aware initializing can just fail from time to time for reasons I do not know. The timing of the containers _might_ be the reason, and if that's the case some better coordination between `superset-init` and the other containers would then be needed (like a `wait-for-init.sh` such as the one described in the Docker docs) to actually fix the issue.
---
Simply said, until the _real_ reasons are found and fixed, if you are facing this issue:
1. just `CTRL+C` then remove the containers **and their volumes** with the `-v` option :
`docker-compose -f docker-compose-non-dev.yml down -v`
2. restart and enjoy:
`docker-compose -f docker-compose-non-dev.yml down`
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] crucialfelix edited a comment on issue #16247: docker-compose non-dev superset-init fails to migrate database
Posted by GitBox <gi...@apache.org>.
crucialfelix edited a comment on issue #16247:
URL: https://github.com/apache/superset/issues/16247#issuecomment-925637079
I did get it to initialize by running:
```
docker-compose up superset-init
```
Let it finish initializing, then you can bring up the whole "cluster"
I think it can be fixed by changing the other services from:
depends_on: *superset-depends-on
to:
depends_on: superset-init
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org