garyng opened a new issue, #20265:
URL: https://github.com/apache/superset/issues/20265
### Helm
Chart version: `0.6.2`
Image tag: `1.5.1rc1`
Values:
```yml
init:
adminUser:
username: [email protected]
postgresql:
enabled: false
supersetNode:
connections:
db_host: [REDACTED]
db_name: [REDACTED]
db_pass: [REDACTED]
db_port: "[REDACTED]"
db_user: [REDACTED]
```
### Stack trace
1st init job:
```
WARNING: You are using pip version 21.2.4; however, version 22.1.2 is
available.
You should consider upgrading via the '/usr/local/bin/python -m pip install
--upgrade pip' command.
Upgrading DB schema...
logging was configured successfully
2022-06-04 06:07:05,260:INFO:superset.utils.logging_configurator:logging was
configured successfully
2022-06-04 06:07:05,265:INFO:root:Configured event logger of type <class
'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata
database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is
recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching
backend for production deployments
2022-06-04 06:07:05,268: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 recommended to use
`RedisCache`, `MemcachedCache` or another dedicated caching backend for
production deployments
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
recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching
backend for production deployments
2022-06-04 06:07:05,272: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 recommended to use
`RedisCache`, `MemcachedCache` or another dedicated caching backend for
production deployments
2022-06-04 06:07:06,088:ERROR:flask_appbuilder.security.sqla.manager:DB
Creation and initialization failed: (psycopg2.errors.UniqueViolation) duplicate
key value violates unique constraint "pg_type_typname_nsp_index"
DETAIL: Key (typname, typnamespace)=(ab_permission_view, 2200) already
exists.
[SQL:
CREATE TABLE ab_permission_view (
id INTEGER NOT NULL,
permission_id INTEGER,
view_menu_id INTEGER,
PRIMARY KEY (id),
UNIQUE (permission_id, view_menu_id),
FOREIGN KEY(permission_id) REFERENCES ab_permission (id),
FOREIGN KEY(view_menu_id) REFERENCES ab_view_menu (id)
)
]
(Background on this error at: http://sqlalche.me/e/13/gkpj)
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py
```
subsequent init job:
```
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/query.py",
line 3535, in __iter__
return self._execute_and_instances(context)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/query.py",
line 3560, in _execute_and_instances
result = conn.execute(querycontext.statement, self._params)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py",
line 1011, in execute
return meth(self, multiparams, params)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py",
line 298, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py",
line 1124, in _execute_clauseelement
ret = self._execute_context(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py",
line 1316, in _execute_context
self._handle_dbapi_exception(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py",
line 1510, in _handle_dbapi_exception
util.raise_(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/compat.py",
line 182, in raise_
raise exception
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py",
line 1276, in _execute_context
self.dialect.do_execute(
File
"/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line
608, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation
"ab_permission_view_role" does not exist
LINE 2: FROM ab_role LEFT OUTER JOIN (ab_permission_view_role AS ab_...
^
[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
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]
(Background on this error at: http://sqlalche.me/e/13/f405)
```
### Environment
- superset version: `superset version`
```
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Superset 0.0.0dev
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
```
- python version: `python --version`
```
Python 3.8.12
```
- node.js version: `node -v`: Not found
- any feature flags active: None
### Checklist
- [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
- #19836 seems to be related
--
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]
