boulund commented on issue #17822: URL: https://github.com/apache/superset/issues/17822#issuecomment-1285527202
I have an existing installation that is labelled as `0.999.0dev` that we have been running since just before version 1.0 came out and that works just fine, deployed with docker-compose. I have been wanting to make a new fresh deployment of the latest version and recently tried deploying Superset version 2 with docker-compose in the same way. I am also experiencing what appears to be the same issue. I've made a completely fresh git clone and have been trying to run checkouts of git tags `2.0.0`, `2.0.1rc1`, and `2.0.1rc2` and I am trying to run Superset with the `docker-compose-non-dev.yml` file as described in https://superset.apache.org/docs/installation/installing-superset-using-docker-compose/#3-launch-superset-through-docker-compose. I have made modifications to the `docker-compose-non-dev.yml` file so it should not interfere with our existing deployment (that is extensively used). I have changed the container names (added a `prod_` prefix) and modified the docker volumes used (appended `_prod`) and changed the port from 8088 to 9099. However, I cannot get these later versions to run. I also observe lots of errors when starting the containers (sorry for the messy copy-paste job, this covered many pages of my tmux terminal window): ``` [superset_prod]$ sudo docker-compose -f docker-compose-non-dev.yml up Creating network "superset_prod_default" with the default driver Creating prod_superset_db ... done Creating prod_superset_cache ... done Creating prod_superset_worker_beat ... done Creating prod_superset_worker ... done Creating prod_superset_init ... done Creating prod_superset_app ... done Attaching to prod_superset_cache, prod_superset_db, prod_superset_init, prod_superset_worker_beat, prod_superset_work r, prod_superset_app prod_superset_cache | 1:C 20 Oct 2022 13:05:05.666 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo prod_superset_cache | 1:C 20 Oct 2022 13:05:05.666 # Redis version=7.0.5, bits=64, commit=00000000, modified=0, p d=1, just started prod_superset_cache | 1:C 20 Oct 2022 13:05:05.666 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf prod_superset_app | Skipping local overrides prod_superset_app | Starting web app... prod_superset_cache | 1:M 20 Oct 2022 13:05:05.667 * monotonic clock: POSIX clock_gettime prod_superset_db | prod_superset_db | PostgreSQL Database directory appears to contain a database; Skipping initialization prod_superset_db | prod_superset_cache | 1:M 20 Oct 2022 13:05:05.668 * Running mode=standalone, port=6379. prod_superset_db | 2022-10-20 13:05:05.772 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 prod_superset_db | 2022-10-20 13:05:05.772 UTC [1] LOG: listening on IPv6 address "::", port 5432 prod_superset_db | 2022-10-20 13:05:05.774 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQ .5432" prod_superset_cache | 1:M 20 Oct 2022 13:05:05.668 # WARNING: The TCP backlog setting of 511 cannot be enforced b cause /proc/sys/net/core/somaxconn is set to the lower value of 128. prod_superset_cache | 1:M 20 Oct 2022 13:05:05.668 # Server initialized prod_superset_cache | 1:M 20 Oct 2022 13:05:05.668 # WARNING overcommit_memory is set to 0! Background save may f il under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot o run the command 'sysctl vm.overcommit_memory=1' for this to take effect. prod_superset_db | 2022-10-20 13:05:05.793 UTC [26] LOG: database system was shut down at 2022-10-20 12:56:45 UTC prod_superset_cache | 1:M 20 Oct 2022 13:05:05.670 * Loading RDB produced by version 7.0.5 prod_superset_cache | 1:M 20 Oct 2022 13:05:05.670 * RDB age 500 seconds prod_superset_cache | 1:M 20 Oct 2022 13:05:05.670 * RDB memory usage when created 2.18 Mb prod_superset_init | Skipping local overrides prod_superset_cache | 1:M 20 Oct 2022 13:05:05.671 * Done loading RDB, keys loaded: 34, keys expired: 0. prod_superset_cache | 1:M 20 Oct 2022 13:05:05.671 * DB loaded from disk: 0.001 seconds prod_superset_cache | 1:M 20 Oct 2022 13:05:05.671 * Ready to accept connections prod_superset_worker | Skipping local overrides prod_superset_init | prod_superset_init | ###################################################################### prod_superset_init | prod_superset_init | prod_superset_init | Init Step 1/4 [Starting] -- Applying DB migrations prod_superset_init | prod_superset_init | prod_superset_init | ###################################################################### prod_superset_init | prod_superset_db | 2022-10-20 13:05:05.801 UTC [1] LOG: database system is ready to accept connections prod_superset_worker | Starting Celery worker... prod_superset_worker_beat | Skipping local overrides prod_superset_worker_beat | Starting Celery beat... prod_superset_app | [2022-10-20 13:05:07 +0000] [9] [INFO] Starting gunicorn 20.1.0 prod_superset_app | [2022-10-20 13:05:07 +0000] [9] [INFO] Listening at: http://0.0.0.0:8088 (9) prod_superset_app | [2022-10-20 13:05:07 +0000] [9] [INFO] Using worker: gthread prod_superset_app | [2022-10-20 13:05:07 +0000] [11] [INFO] Booting worker with pid: 11 prod_superset_worker_beat | -------------------------------------------------------------------------------- prod_superset_worker_beat | WARNING prod_superset_worker_beat | -------------------------------------------------------------------------------- prod_superset_worker_beat | A Default SECRET_KEY was detected, please use superset_config.py to override it. prod_superset_worker_beat | Use a strong complex alphanumeric string and use a tool to help you generate prod_superset_worker_beat | a sufficiently random sequence, ex: openssl rand -base64 42 prod_superset_worker_beat | -------------------------------------------------------------------------------- prod_superset_worker_beat | -------------------------------------------------------------------------------- prod_superset_worker_beat | logging was configured successfully prod_superset_worker_beat | 2022-10-20 13:05:09,249:INFO:superset.utils.logging_configurator:logging was configured s ccessfully prod_superset_worker_beat | 2022-10-20 13:05:09,251:INFO:root:Configured event logger of type <class 'superset.utils. og.DBEventLogger'> prod_superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the fo lowing cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicat d caching backend for production deployments prod_superset_worker_beat | 2022-10-20 13:05:09,254:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recomme ded to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_worker_beat | Falling back to the built-in cache, that stores data in the metadata database, for the fo lowing cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another de icated caching backend for production deployments prod_superset_worker_beat | 2022-10-20 13:05:09,259:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is re ommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_app | -------------------------------------------------------------------------------- prod_superset_app | WARNING prod_superset_app | -------------------------------------------------------------------------------- prod_superset_app | A Default SECRET_KEY was detected, please use superset_config.py to override it. prod_superset_app | Use a strong complex alphanumeric string and use a tool to help you generate prod_superset_app | a sufficiently random sequence, ex: openssl rand -base64 42 prod_superset_app | -------------------------------------------------------------------------------- prod_superset_app | -------------------------------------------------------------------------------- prod_superset_app | logging was configured successfully prod_superset_app | 2022-10-20 13:05:09,366:INFO:superset.utils.logging_configurator:logging was configured suc essfully prod_superset_app | 2022-10-20 13:05:09,372:INFO:root:Configured event logger of type <class 'superset.utils.lo .DBEventLogger'> prod_superset_app | Falling back to the built-in cache, that stores data in the metadata database, for the foll wing cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_app | 2022-10-20 13:05:09,376:WARNING:superset.utils.cache_manager:Falling back to the built-in c che, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommend d to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_app | Falling back to the built-in cache, that stores data in the metadata database, for the foll wing cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedi ated caching backend for production deployments prod_superset_app | 2022-10-20 13:05:09,382:WARNING:superset.utils.cache_manager:Falling back to the built-in c che, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is reco mended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_worker | -------------------------------------------------------------------------------- prod_superset_worker | WARNING prod_superset_worker | -------------------------------------------------------------------------------- prod_superset_worker | A Default SECRET_KEY was detected, please use superset_config.py to override it. prod_superset_worker | Use a strong complex alphanumeric string and use a tool to help you generate prod_superset_worker | a sufficiently random sequence, ex: openssl rand -base64 42 prod_superset_worker | -------------------------------------------------------------------------------- prod_superset_worker | -------------------------------------------------------------------------------- prod_superset_worker | logging was configured successfully prod_superset_worker | 2022-10-20 13:05:09,460:INFO:superset.utils.logging_configurator:logging was configured suc essfully prod_superset_worker | 2022-10-20 13:05:09,463:INFO:root:Configured event logger of type <class 'superset.utils.lo .DBEventLogger'> prod_superset_worker | Falling back to the built-in cache, that stores data in the metadata database, for the foll wing cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_worker | 2022-10-20 13:05:09,466:WARNING:superset.utils.cache_manager:Falling back to the built-in c che, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommende d to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_worker | Falling back to the built-in cache, that stores data in the metadata database, for the follo wing cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedic ated caching backend for production deployments prod_superset_worker | 2022-10-20 13:05:09,473:WARNING:superset.utils.cache_manager:Falling back to the built-in ca che, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recom mended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_init | -------------------------------------------------------------------------------- prod_superset_init | WARNING prod_superset_init | -------------------------------------------------------------------------------- prod_superset_init | A Default SECRET_KEY was detected, please use superset_config.py to override it. prod_superset_init | Use a strong complex alphanumeric string and use a tool to help you generate prod_superset_init | a sufficiently random sequence, ex: openssl rand -base64 42 prod_superset_init | -------------------------------------------------------------------------------- prod_superset_init | -------------------------------------------------------------------------------- prod_superset_init | logging was configured successfully prod_superset_init | 2022-10-20 13:05:09,795:INFO:superset.utils.logging_configurator:logging was configured succ essfully prod_superset_init | 2022-10-20 13:05:09,800:INFO:root:Configured event logger of type <class 'superset.utils.log .DBEventLogger'> prod_superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the follo wing cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_init | 2022-10-20 13:05:09,803:WARNING:superset.utils.cache_manager:Falling back to the built-in ca che, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommende d to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_init | Falling back to the built-in cache, that stores data in the metadata database, for the follo wing cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedic ated caching backend for production deployments prod_superset_init | 2022-10-20 13:05:09,808:WARNING:superset.utils.cache_manager:Falling back to the built-in ca che, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recom mended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments prod_superset_worker_beat | /usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:68: SAWar ning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if t hese relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() anno tation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzy x) prod_superset_worker_beat | for prop in class_mapper(obj).iterate_properties: prod_superset_worker_beat | [2022-10-20 13:05:11,250: INFO/MainProcess] beat: Starting... prod_superset_worker_beat | [2022-10-20 13:05:11,262: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler) prod_superset_init | /usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:68: SAWarni ng: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with re lationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if the se relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they ar e read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annota tion can be used to isolate the columns that should be written towards. To silence this warning, add the parameter ' overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) prod_superset_init | for prop in class_mapper(obj).iterate_properties: prod_superset_init | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. prod_superset_init | INFO [alembic.runtime.migration] Will assume transactional DDL. prod_superset_worker | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] prod_superset_worker | prod_superset_worker | -------------- celery@f17a90542dda v5.2.2 (dawn-chorus) prod_superset_worker | --- ***** ----- prod_superset_worker | -- ******* ---- Linux-4.18.0-365.el8.x86_64-x86_64-with-glibc2.2.5 2022-10-20 13:05:11 prod_superset_worker | - *** --- * --- prod_superset_worker | - ** ---------- [config] prod_superset_worker | - ** ---------- .> app: __main__:0x7f52a03de0a0 prod_superset_worker | - ** ---------- .> transport: redis://redis:6379/0 prod_superset_worker | - ** ---------- .> results: redis://redis:6379/1 prod_superset_worker | - *** --- * --- .> concurrency: 96 (prefork) prod_superset_worker | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) prod_superset_worker | --- ***** ----- prod_superset_worker | -------------- [queues] prod_superset_worker | .> celery exchange=celery(direct) key=celery prod_superset_worker | prod_superset_worker | prod_superset_worker | [tasks] prod_superset_worker | . cache-warmup prod_superset_worker | . cache_chart_thumbnail prod_superset_worker | . cache_dashboard_thumbnail prod_superset_worker | . fetch_url prod_superset_worker | . load_chart_data_into_cache prod_superset_worker | . load_explore_json_into_cache prod_superset_worker | . reports.execute prod_superset_worker | . reports.prune_log prod_superset_worker | . reports.scheduler prod_superset_worker | . sql_lab.get_sql_results prod_superset_worker | prod_superset_worker | /usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:68: SAWarni ng: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with re lationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if the se relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they ar e read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annota tion can be used to isolate the columns that should be written towards. To silence this warning, add the parameter ' overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) prod_superset_worker | for prop in class_mapper(obj).iterate_properties: prod_superset_worker | /usr/local/lib/python3.8/site-packages/celery/platforms.py:840: SecurityWarning: You're runn ing the worker with superuser privileges: this is prod_superset_worker | absolutely not recommended! prod_superset_worker | prod_superset_worker | Please specify a different user using the --uid option. prod_superset_worker | prod_superset_worker | User information: uid=0 euid=0 gid=0 egid=0 prod_superset_worker | prod_superset_worker | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'CELERYBEAT_SCHEDULE' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the beat_schedule instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'CELERY_RESULT_BACKEND' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the result_backend instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'CELERY_IMPORTS' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the imports instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'CELERYD_PREFETCH_MULTIPLIER' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the worker_prefetch_multiplier instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'CELERY_ACKS_LATE' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the task_acks_late instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] /usr/local/lib/python3.8/site-packages/celery /app/utils.py:204: CDeprecationWarning: prod_superset_worker | The 'BROKER_URL' setting is deprecated and scheduled for removal in prod_superset_worker | version 6.0.0. Use the broker_url instead prod_superset_worker | prod_superset_worker | deprecated.warn(description=f'The {setting!r} setting', prod_superset_worker | prod_superset_worker | [2022-10-20 13:05:11,725: WARNING/MainProcess] Please run `celery upgrade settings path/to/s ettings.py` to avoid these warnings and to allow a smoother upgrade to Celery 6.0. prod_superset_init | INFO [alembic.runtime.migration] Running upgrade -> 4e6a06bad7a8, Init prod_superset_init | INFO [alembic.runtime.migration] Running upgrade 4e6a06bad7a8 -> 5a7bad26f2a7, empty messag e prod_superset_init | INFO [alembic.runtime.migration] Running upgrade 5a7bad26f2a7 -> 1e2841a4128, empty message prod_superset_init | INFO [alembic.runtime.migration] Running upgrade 1e2841a4128 -> 2929af7925ed, TZ offsets in data sources prod_superset_init | INFO [alembic.runtime.migration] Running upgrade 2929af7925ed -> 289ce07647b, Add encrypted password field prod_superset_init | INFO [alembic.runtime.migration] Running upgrade 289ce07647b -> 1a48a5411020, adding slug t o dash .... lots of alembic migration lines removed for brevity ... prod_superset_db | 2022-10-20 13:05:14.425 UTC [37] ERROR: relation "ab_permission_view_role" does not exist at character 292 prod_superset_db | 2022-10-20 13:05:14.425 UTC [37] STATEMENT: SELECT ab_role.id AS ab_role_id, ab_rol e.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 prod_superset_db | FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_permission_view_ro le_1 JOIN ab_permission_view AS ab_permission_view_1 ON ab_permission_view_1.id = ab_permission_view_role_1.pe rmission_view_id) ON ab_role.id = ab_permission_view_role_1.role_id prod_superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] prod_superset_init | Cleaning up slice uuid from dashboard position json.. Done. osition json.. prod_superset_init | prod_superset_init | Traceback (most recent call last): prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1819 , in _execute_context prod_superset_init | self.dialect.do_execute( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 7 32, in do_execute prod_superset_init | cursor.execute(statement, parameters) prod_superset_init | psycopg2.errors.UndefinedTable: relation "ab_permission_view_role" does not exist prod_superset_init | LINE 2: FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_... prod_superset_init | ^ prod_superset_init | prod_superset_init | prod_superset_init | The above exception was the direct cause of the following exception: prod_superset_init | prod_superset_init | Traceback (most recent call last): prod_superset_init | File "/usr/local/bin/superset", line 33, in <module> prod_superset_init | sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')()) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1128, in __call_ _ prod_superset_init | return self.main(*args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 601, in main prod_superset_init | return super().main(*args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1053, in main prod_superset_init | rv = self.invoke(ctx) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke prod_superset_init | return _process_result(sub_ctx.command.invoke(sub_ctx)) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke prod_superset_init | return _process_result(sub_ctx.command.invoke(sub_ctx)) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1395, in invoke prod_superset_init | return ctx.invoke(self.callback, **ctx.params) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke prod_superset_init | return __callback(*args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 26, in new _func prod_superset_init | return f(get_current_context(), *args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 445, in decorator prod_superset_init | return __ctx.invoke(f, *args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke prod_superset_init | return __callback(*args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/flask_migrate/cli.py", line 149, in u pgrade prod_superset_init | _upgrade(directory, revision, sql, tag, x_arg) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 98, in wrapped prod_superset_init | f(*args, **kwargs) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 185, in upgrade prod_superset_init | command.upgrade(config, revision, sql=sql, tag=tag) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 294, in upg rade prod_superset_init | script.run_env() prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 490, in run_env prod_superset_init | util.load_python_file(self.dir, "env.py") prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 97, in load_python_file prod_superset_init | module = load_module_py(module_id, path) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 184, in load_module_py prod_superset_init | spec.loader.exec_module(module) prod_superset_init | File "<frozen importlib._bootstrap_external>", line 843, in exec_module prod_superset_init | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed prod_superset_init | File "/app/superset/extensions/../migrations/env.py", line 126, in <module> prod_superset_init | run_migrations_online() prod_superset_init | File "/app/superset/extensions/../migrations/env.py", line 118, in run_migrations_ online prod_superset_init | context.run_migrations() prod_superset_init | File "<string>", line 8, in run_migrations prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/runtime/environment.py", line 813, in run_migrations prod_superset_init | self.get_context().run_migrations(**kw) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/alembic/runtime/migration.py", line 5 61, in run_migrations prod_superset_init | step.migration_fn(**kw) prod_superset_init | File "/app/superset/migrations/versions/2020-11-20_14-24_e38177dbf641_security_con verge_saved_queries.py", line 100, in upgrade prod_superset_init | migrate_roles(session, PVM_MAP) prod_superset_init | File "/app/superset/migrations/shared/security_converge.py", line 237, in migrate_ roles prod_superset_init | roles = session.query(Role).options(Load(Role).joinedload(Role.permissions)).all () prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 2768, in all prod_superset_init | return self._iter().all() prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 2903, in _iter prod_superset_init | result = self.session.execute( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 1696 , in execute prod_superset_init | result = conn._execute_20(statement, params or {}, execution_options) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1631 prod_superset_init | return meth(self, args_10style, kwargs_10style, execution_options) prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 325 , in _execute_on_connection prod_superset_init | return connection._execute_clauseelement( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1498 , in _execute_clauseelement prod_superset_init | ret = self._execute_context( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1862 , in _execute_context prod_superset_init | self._handle_dbapi_exception( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 2043 , in _handle_dbapi_exception prod_superset_init | util.raise_( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 207, in raise_ prod_superset_init | raise exception prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1819 , in _execute_context prod_superset_init | self.dialect.do_execute( prod_superset_init | File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 7 32, in do_execute prod_superset_init | cursor.execute(statement, parameters) prod_superset_init | sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation "ab_permi ssion_view_role" does not exist prod_superset_init | LINE 2: FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_... prod_superset_init | ^ prod_superset_init | prod_superset_init | [SQL: SELECT ab_role.id AS ab_role_id, ab_role.name AS ab_role_name, ab_permission_v iew_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 prod_superset_init | FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_permission_view_role_1 J OIN ab_permission_view AS ab_permission_view_1 ON ab_permission_view_1.id = ab_permission_view_role_1.permissi on_view_id) ON ab_role.id = ab_permission_view_role_1.role_id] prod_superset_init | (Background on this error at: https://sqlalche.me/e/14/f405) ``` As you can see it seems to be similar to the errors described by @MCBoarder289 . I also get > 500 Internal server error > Sorry, something went wrong. We are fixing the mistake now. Try again later or go back to home. when I try to access Superset in the browser at localhost:9099. The commands recommended by @IvanRibakov earlier seem to be intended for a pure docker-based deployment, not the docker-compose based one. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
