3a8452c65d
Check if a table already exists before creating it. This prevents the errors: INFO migrate.versioning.api [designate-manage - - - - -] 69 -> 70... CRITICAL designate [designate-manage - - - - -] ProgrammingError: \ (psycopg2.ProgrammingError) type "resource_statuses" already exists INFO migrate.versioning.api [designate-manage - - - - -] 85 -> 86... CRITICAL designate [designate-manage - - - - -] ProgrammingError: (psycopg2.ProgrammingError) relation "unique_pool_host_port" already exists INFO migrate.versioning.api [designate-manage - - - - -] 96 -> 97... CRITICAL designate [designate-manage - - - - -] ProgrammingError: (psycopg2.ProgrammingError) type "service_statuses" already exists ERROR designate ProgrammingError: (psycopg2.ProgrammingError) type "service_statuses" already exists ERROR designate HINT: A relation has an associated type of the same name, so you must use a name that doesn't conflict with any existing type. when running the migration with postgresql. Closes-Bug: #1640453 Change-Id: I3e8928c1b92d5c42e634abb992a4d931c44be01b |
||
---|---|---|
.. | ||
__init__.py | ||
base.py | ||
session.py | ||
types.py | ||
utils.py |