Fresh install of Zun-10.0.0.0rc1 on Zed release using Postgresql 10.22 + python3-psycopg2
"zun-db-manage upgrade" results in multiple failures:
First issue:
zun-db-manage upgrade
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade -> a9a92eebd9a8, create_table_zun_service
INFO [alembic.runtime.migration] Running upgrade a9a92eebd9a8 -> 9fe371393a24, create_table_container
INFO [alembic.runtime.migration] Running upgrade 9fe371393a24 -> 5971a6844738, add container_id column to container
INFO [alembic.runtime.migration] Running upgrade 5971a6844738 -> 93fbb05b77b9, add memory field to container
INFO [alembic.runtime.migration] Running upgrade 93fbb05b77b9 -> 63a08e32cc43, add task state to container
INFO [alembic.runtime.migration] Running upgrade 63a08e32cc43 -> 1192ba19a6e9, Add cpu workdir ports hostname labels to container
INFO [alembic.runtime.migration] Running upgrade 1192ba19a6e9 -> 72c6947c6636, create_table_image
INFO [alembic.runtime.migration] Running upgrade 72c6947c6636 -> c5565cbaa3de, Insert status_reason to Container table
INFO [alembic.runtime.migration] Running upgrade c5565cbaa3de -> 43e1088c3389, add image_pull_policy column
INFO [alembic.runtime.migration] Running upgrade 43e1088c3389 -> 4a0c4f7a4a33, add meta addresses to container
INFO [alembic.runtime.migration] Running upgrade 4a0c4f7a4a33 -> 531e4a890480, add host to container
INFO [alembic.runtime.migration] Running upgrade 531e4a890480 -> bbcfa910a8a5, add_restart_policy_column
INFO [alembic.runtime.migration] Running upgrade bbcfa910a8a5 -> ad43a2179cf2, add_status_detail
INFO [alembic.runtime.migration] Running upgrade ad43a2179cf2 -> d1ef05fd92c8, add tty stdin_open
INFO [alembic.runtime.migration] Running upgrade d1ef05fd92c8 -> 5458f8394206, add image driver field
INFO [alembic.runtime.migration] Running upgrade 5458f8394206 -> 6fd4f7582eb0, Add resource provider table
INFO [alembic.runtime.migration] Running upgrade 6fd4f7582eb0 -> 7975b7f0f792, Add resource class table
INFO [alembic.runtime.migration] Running upgrade 7975b7f0f792 -> 09f196622a3f, create inventory table
INFO [alembic.runtime.migration] Running upgrade 09f196622a3f -> e4d145e195f4, Create allocation table
INFO [alembic.runtime.migration] Running upgrade e4d145e195f4 -> 8192905fd835, add uuid_to_resource_class
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context
self.dialect.do_execute(
File "/usr/local/lib64/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
cursor.execute(statement, parameters)
psycopg2.errors.DependentObjectsStillExist: cannot drop index uniq_container0name because constraint uniq_container0name on table resource_class requires it
HINT: You can drop constraint uniq_container0name on table resource_class instead.
I manually skipped past this issue by removing the uniq_container0name details from:
zun/db/sqlalchemy/alembic/versions/7975b7f0f792_add_resource_class_table.py
zun/db/sqlalchemy/alembic/versions/8192905fd835_add_uuid_to_resource_class.py
Second issue/attempt:
zun-db-manage upgrade
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade -> a9a92eebd9a8, create_table_zun_service
INFO [alembic.runtime.migration] Running upgrade a9a92eebd9a8 -> 9fe371393a24, create_table_container
....
INFO [alembic.runtime.migration] Running upgrade 3e80bbfd8da7 -> 105626c4f972, add privileged to container
INFO [alembic.runtime.migration] Running upgrade 105626c4f972 -> 2fb377a5a519, add healthcheck to containers
INFO [alembic.runtime.migration] Running upgrade 2fb377a5a519 -> f746cd28bcac, add host to volume mapping
INFO [alembic.runtime.migration] Running upgrade f746cd28bcac -> bc56b9932dd9, add runtime to compute node
INFO [alembic.runtime.migration] Running upgrade bc56b9932dd9 -> a9c9fb54274a, add_contents_to_volume_mapping_table
INFO [alembic.runtime.migration] Running upgrade a9c9fb54274a -> a019998b09b5, add host to image
INFO [alembic.runtime.migration] Running upgrade a019998b09b5 -> 02134de8e7d3, add_exposed_ports_to_container
INFO [alembic.runtime.migration] Running upgrade 02134de8e7d3 -> 54bcb75afb32, Add init containers uuids to capsule
INFO [alembic.runtime.migration] Running upgrade 54bcb75afb32 -> 35cb52c5553f, rename volume_id to cinder_volume_id in volume_mapping
INFO [alembic.runtime.migration] Running upgrade 35cb52c5553f -> 33cdd98bb9b2, split volume_mapping table
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context
self.dialect.do_execute(
File "/usr/local/lib64/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
cursor.execute(statement, parameters)
psycopg2.errors.DuplicateTable: relation "uniq_volume0uuid" already exists
