Failed to upgrade metabase from 0.45.3 to the latest

andresg · January 10, 2024, 5:32pm

Hi im trying to upgrade my self hosted metabase but i was have a issue to do it. Im using postgresql and a docker intance.

2024-01-10 17:23:32,794 INFO metabase.core :: System info:
metabase-metabase-1  |  {"file.encoding" "UTF-8",
metabase-metabase-1  |  "java.runtime.name" "OpenJDK Runtime Environment",
metabase-metabase-1  |  "java.runtime.version" "11.0.21+9",
metabase-metabase-1  |  "java.vendor" "Eclipse Adoptium",
metabase-metabase-1  |  "java.vendor.url" "https://adoptium.net/",
metabase-metabase-1  |  "java.version" "11.0.21",
metabase-metabase-1  |  "java.vm.name" "OpenJDK 64-Bit Server VM",
metabase-metabase-1  |  "java.vm.version" "11.0.21+9",
metabase-metabase-1  |  "os.name" "Linux",
metabase-metabase-1  |  "os.version" "5.10.16.3-microsoft-standard-WSL2",
metabase-metabase-1  |  "user.language" "en",
metabase-metabase-1  |  "user.timezone" "UTC"}


2024-01-10 17:23:33,771 INFO db.liquibase :: Database has unrun migrations. Waiting for migration lock to be cleared...
metabase-metabase-1  | 2024-01-10 17:23:33,827 INFO db.liquibase :: Migration lock is cleared. Running 162 migrations ...
metabase-db-1        | 2024-01-10 17:23:34.072 UTC [82] ERROR:  column "database_id" of relation "query_action" already exists
metabase-db-1        | 2024-01-10 17:23:34.072 UTC [82] STATEMENT:  ALTER TABLE "public"."query_action" ADD "database_id" INTEGER
metabase-db-1        | 2024-01-10 17:23:34.074 UTC [82] ERROR:  current transaction is aborted, commands ignored until end of transaction block
metabase-db-1        | 2024-01-10 17:23:34.074 UTC [82] STATEMENT:  
metabase-metabase-1  | 2024-01-10 17:23:34,075 ERROR liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v46.00-008::snoe encountered an exception.
metabase-metabase-1  | 2024-01-10 17:23:34,085 ERROR middleware.log :: GET /api/health 503 220.3 µs (0 DB calls) 
metabase-metabase-1  | {:status "initializing", :progress 0.3}
metabase-metabase-1  | 
metabase-metabase-1  | 2024-01-10 17:23:34,091 ERROR metabase.core :: Metabase Initialization FAILED
metabase-metabase-1  | liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v46.00-008::snoe:
metabase-metabase-1  |      Reason: liquibase.exception.DatabaseException: ERROR: column "database_id" of relation "query_action" already exists [Failed SQL: (0) ALTER TABLE "public"."query_action" ADD "database_id" INTEGER]
metabase-metabase-1  |  at liquibase.command.CommandScope.execute(CommandScope.java:235)
metabase-metabase-1  |  at liquibase.Liquibase.lambda$update$0(Liquibase.java:237)
metabase-metabase-1  |  at liquibase.Scope.lambda$child$0(Scope.java:194)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:203)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:193)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:172)
metabase-metabase-1  |  at liquibase.Liquibase.runInScope(Liquibase.java:1618)
metabase-metabase-1  |  at liquibase.Liquibase.update(Liquibase.java:229)
metabase-metabase-1  |  at liquibase.Liquibase.update(Liquibase.java:213)
metabase-metabase-1  |  at liquibase.Liquibase.update(Liquibase.java:198)
metabase-metabase-1  |  at metabase.db.liquibase$migrate_up_if_needed_BANG_.invokeStatic(liquibase.clj:224)
metabase-metabase-1  |  at metabase.db.liquibase$migrate_up_if_needed_BANG_.invoke(liquibase.clj:209)
metabase-metabase-1  |  at metabase.db.setup$fn__50307$_AMPERSAND_f__50308$fn__50309.invoke(setup.clj:80)
metabase-metabase-1  |  at metabase.db.liquibase$fn__47828$_AMPERSAND_f__47829.invoke(liquibase.clj:131)
metabase-metabase-1  |  at metabase.db.liquibase$fn__47828$fn__47831.invoke(liquibase.clj:124)
metabase-metabase-1  |  at metabase.db.setup$fn__50307$_AMPERSAND_f__50308.doInvoke(setup.clj:75)
metabase-metabase-1  |  at clojure.lang.RestFn.invoke(RestFn.java:445)
metabase-metabase-1  |  at clojure.lang.AFn.applyToHelper(AFn.java:160)
metabase-metabase-1  |  at clojure.lang.RestFn.applyTo(RestFn.java:132)
metabase-metabase-1  |  at clojure.core$apply.invokeStatic(core.clj:673)
metabase-metabase-1  |  at clojure.core$apply.invoke(core.clj:662)
metabase-metabase-1  |  at metabase.db.setup$fn__50307$fn__50317.doInvoke(setup.clj:56)
metabase-metabase-1  |  at clojure.lang.RestFn.invoke(RestFn.java:445)
metabase-metabase-1  |  at metabase.db.setup$fn__50345$_AMPERSAND_f__50346.invoke(setup.clj:148)
metabase-metabase-1  |  at metabase.db.setup$fn__50345$fn__50352.invoke(setup.clj:142)
metabase-metabase-1  |  at metabase.db.setup$fn__50355$_AMPERSAND_f__50356$fn__50359$fn__50360.invoke(setup.clj:166)
metabase-metabase-1  |  at metabase.util.jvm$do_with_us_locale.invokeStatic(jvm.clj:239)
metabase-metabase-1  |  at metabase.util.jvm$do_with_us_locale.invoke(jvm.clj:225)
metabase-metabase-1  |  at metabase.db.setup$fn__50355$_AMPERSAND_f__50356$fn__50359.invoke(setup.clj:161)
metabase-metabase-1  |  at metabase.db.setup$fn__50355$_AMPERSAND_f__50356.invoke(setup.clj:160)
metabase-metabase-1  |  at metabase.db.setup$fn__50355$fn__50367.invoke(setup.clj:154)
metabase-metabase-1  |  at metabase.db$setup_db_BANG_$fn__50376.invoke(db.clj:69)
metabase-metabase-1  |  at metabase.db$setup_db_BANG_.invokeStatic(db.clj:64)
metabase-metabase-1  |  at metabase.db$setup_db_BANG_.invoke(db.clj:55)
metabase-metabase-1  |  at metabase.core$init_BANG__STAR_.invokeStatic(core.clj:111)
metabase-metabase-1  |  at metabase.core$init_BANG__STAR_.invoke(core.clj:97)
metabase-metabase-1  |  at metabase.core$init_BANG_.invokeStatic(core.clj:154)
metabase-metabase-1  |  at metabase.core$init_BANG_.invoke(core.clj:149)
metabase-metabase-1  |  at metabase.core$start_normally.invokeStatic(core.clj:166)
metabase-metabase-1  |  at metabase.core$start_normally.invoke(core.clj:160)
metabase-metabase-1  |  at metabase.core$entrypoint.invokeStatic(core.clj:199)
metabase-metabase-1  |  at metabase.core$entrypoint.doInvoke(core.clj:193)
metabase-metabase-1  |  at clojure.lang.RestFn.invoke(RestFn.java:397)
metabase-metabase-1  |  at clojure.lang.AFn.applyToHelper(AFn.java:152)
metabase-metabase-1  |  at clojure.lang.RestFn.applyTo(RestFn.java:132)
metabase-metabase-1  |  at clojure.lang.Var.applyTo(Var.java:705)
metabase-metabase-1  |  at clojure.core$apply.invokeStatic(core.clj:667)
metabase-metabase-1  |  at clojure.core$apply.invoke(core.clj:662)
metabase-metabase-1  |  at metabase.bootstrap$_main.invokeStatic(bootstrap.clj:31)
metabase-metabase-1  |  at metabase.bootstrap$_main.doInvoke(bootstrap.clj:28)
metabase-metabase-1  |  at clojure.lang.RestFn.invoke(RestFn.java:397)
metabase-metabase-1  |  at clojure.lang.AFn.applyToHelper(AFn.java:152)
metabase-metabase-1  |  at clojure.lang.RestFn.applyTo(RestFn.java:132)
metabase-metabase-1  |  at metabase.bootstrap.main(Unknown Source)
metabase-metabase-1  | Caused by: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v46.00-008::snoe:
metabase-metabase-1  |      Reason: liquibase.exception.DatabaseException: ERROR: column "database_id" of relation "query_action" already exists [Failed SQL: (0) ALTER TABLE "public"."query_action" ADD "database_id" INTEGER]
metabase-metabase-1  |  at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:123)
metabase-metabase-1  |  at liquibase.command.core.AbstractUpdateCommandStep.lambda$run$0(AbstractUpdateCommandStep.java:102)
metabase-metabase-1  |  at liquibase.Scope.lambda$child$0(Scope.java:194)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:203)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:193)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:172)
metabase-metabase-1  |  at liquibase.command.core.AbstractUpdateCommandStep.run(AbstractUpdateCommandStep.java:99)
metabase-metabase-1  |  at liquibase.command.CommandScope.execute(CommandScope.java:212)
metabase-metabase-1  |  ... 53 more
metabase-metabase-1  | Caused by: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v46.00-008::snoe:
metabase-metabase-1  |      Reason: liquibase.exception.DatabaseException: ERROR: column "database_id" of relation "query_action" already exists [Failed SQL: (0) ALTER TABLE "public"."query_action" ADD "database_id" INTEGER]
metabase-metabase-1  |  at liquibase.changelog.ChangeSet.execute(ChangeSet.java:761)
metabase-metabase-1  |  at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:61)
metabase-metabase-1  |  at liquibase.changelog.ChangeLogIterator$2.lambda$null$0(ChangeLogIterator.java:111)
metabase-metabase-1  |  at liquibase.Scope.lambda$child$0(Scope.java:194)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:203)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:193)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:172)
metabase-metabase-1  |  at liquibase.changelog.ChangeLogIterator$2.lambda$run$1(ChangeLogIterator.java:111)
metabase-metabase-1  |  at liquibase.Scope.lambda$child$0(Scope.java:194)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:203)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:193)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:172)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:260)
metabase-metabase-1  |  at liquibase.changelog.ChangeLogIterator$2.run(ChangeLogIterator.java:94)
metabase-metabase-1  |  at liquibase.Scope.lambda$child$0(Scope.java:194)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:203)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:193)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:172)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:260)
metabase-metabase-1  |  at liquibase.Scope.child(Scope.java:264)
metabase-metabase-1  |  at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:68)
metabase-metabase-1  |  ... 60 more
metabase-metabase-1  | Caused by: liquibase.exception.DatabaseException: ERROR: column "database_id" of relation "query_action" already exists [Failed SQL: (0) ALTER TABLE "public"."query_action" ADD "database_id" INTEGER]
metabase-metabase-1  |  at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:445)
metabase-metabase-1  |  at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:77)
metabase-metabase-1  |  at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:160)
metabase-metabase-1  |  at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1287)
metabase-metabase-1  |  at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1269)
metabase-metabase-1  |  at liquibase.changelog.ChangeSet.execute(ChangeSet.java:718)
metabase-metabase-1  |  ... 80 more
metabase-metabase-1  | Caused by: org.postgresql.util.PSQLException: ERROR: column "database_id" of relation "query_action" already exists
metabase-metabase-1  |  at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)
metabase-metabase-1  |  at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401)
metabase-metabase-1  |  at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:335)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:321)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:297)
metabase-metabase-1  |  at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:292)
metabase-metabase-1  |  at com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:75)
metabase-metabase-1  |  at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:441)
metabase-metabase-1  |  ... 85 more
metabase-metabase-1  | 2024-01-10 17:23:34,098 INFO metabase.core :: Metabase Shutting Down ...
metabase-metabase-1  | 2024-01-10 17:23:34,099 INFO metabase.server :: Shutting Down Embedded Jetty Webserver
metabase-metabase-1  | 2024-01-10 17:23:34,104 INFO metabase.core :: Metabase Shutdown COMPLETE

I understood that the schemas were updated automatically but I don't know what is happening, any suggestions on what I should do to be able to update to the latest version?

andresg · January 10, 2024, 5:35pm

I am currently setting it up in my premises to test before doing it in production. Here is my docker compose file:

services:
  db:
    image: postgres:13.1-alpine
    restart: always
    volumes:
      - db-data:${DB_DATA_DIR}
    environment:
      - PGDATA=${DB_DATA_DIR}
      - POSTGRES_DB=${DB_NAME}
      - POSTGRES_USER=${DB_USER}
      - POSTGRES_PASSWORD=${DB_PASSWORD}
    ports:
      - 5433:5432

  metabase:
    image: metabase/metabase:v0.48.2
    restart: always
    environment:
      MB_DB_TYPE: "postgres"
      MB_DB_DBNAME: "${DB_NAME}"
      MB_DB_PORT: "5432"
      MB_DB_USER: "${DB_USER}"
      MB_DB_PASS: "${DB_PASSWORD}"
      MB_DB_HOST: "db"
      MB_PASSWORD_COMPLEXITY: strong
      MB_PASSWORD_LENGTH: 10
      MB_DB_AUTOMIGRATE: true
      JAVA_TIMEZONE: "${MB_JAVA_TIMEZONE}"
    ports:
      - 127.0.0.1:${MB_PORT}:3000
    extra_hosts:
      - host.docker.internal:host-gateway
    networks:
      default:
        ipv4_address: XXX.XXXX.XXX
    depends_on:
      - db

networks:
  default:
    ipam:
      driver: default
      config:
        - subnet: "XXX.XXX.XXX/24"

volumes:
  db-data:

Luiggi · January 10, 2024, 5:41pm

you seem to have done an upgrade and downgraded without restoring the DB backup...

I would suggest you go first to 46 then 47 and then 48

try that and let me know how it goes

andresg · January 10, 2024, 6:05pm

Thx for the reply @Luiggi i Will try to do that.

And this was be my steps before posting here:

Backup production db
Create a empty db on My local
Load the production db on My empty db
Run the container

I do something wrong?

Luiggi · January 11, 2024, 11:26am

At some point in time there seems to have been an upgrade and downgrade without a restore, that’s why you see a column that shouldn’t be there in the logs

andresg · January 12, 2024, 4:28pm

okay I understand. I tried what you told me but the same error remains. If I create a new db with the latest version of metabase, it is possible to migrate the queries, dashboard, etc. from the old version to the new one? Currently in the company we have the open source self host version.

Luiggi · January 15, 2024, 12:18pm

you should be able to do a "select into" of the tables between versions and move the contents from a version to another one

andresg · January 17, 2024, 7:55pm

We create a new DB and try to restore de data but we recive de follow error:

liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v00.00-000::qnkhuat:
2024-01-17 16:50:14      Reason: liquibase.exception.DatabaseException: ERROR: extension "citext" is not allow-listed for "azure_pg_admin" users in Azure Database for PostgreSQL
2024-01-17 16:50:14   Hint: to see the full allow list of extensions, please run: "show azure.extensions;" [Failed SQL: (0) --
2024-01-17 16:50:14 -- Name: citext; Type: EXTENSION; Schema: -; Owner: -
2024-01-17 16:50:14 --
2024-01-17 16:50:14 
2024-01-17 16:50:14 CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public]
2024-01-17 16:50:14     at liquibase.command.CommandScope.execute(CommandScope.java:235)
2024-01-17 16:50:14     at liquibase.Liquibase.lambda$update$0(Liquibase.java:237)
2024-01-17 16:50:14     at liquibase.Scope.lambda$child$0(Scope.java:194)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:203)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:193)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:172)
2024-01-17 16:50:14     at liquibase.Liquibase.runInScope(Liquibase.java:1618)
2024-01-17 16:50:14     at liquibase.Liquibase.update(Liquibase.java:229)
2024-01-17 16:50:14     at liquibase.Liquibase.update(Liquibase.java:213)
2024-01-17 16:50:14     at liquibase.Liquibase.update(Liquibase.java:198)
2024-01-17 16:50:14     at metabase.db.liquibase$migrate_up_if_needed_BANG_.invokeStatic(liquibase.clj:224)
2024-01-17 16:50:14     at metabase.db.liquibase$migrate_up_if_needed_BANG_.invoke(liquibase.clj:209)
2024-01-17 16:50:14     at metabase.db.setup$fn__50124$_AMPERSAND_f__50125$fn__50126.invoke(setup.clj:80)
2024-01-17 16:50:14     at metabase.db.liquibase$fn__47850$_AMPERSAND_f__47851.invoke(liquibase.clj:131)
2024-01-17 16:50:14     at metabase.db.liquibase$fn__47850$fn__47853.invoke(liquibase.clj:124)
2024-01-17 16:50:14     at metabase.db.setup$fn__50124$_AMPERSAND_f__50125.doInvoke(setup.clj:75)
2024-01-17 16:50:14     at clojure.lang.RestFn.invoke(RestFn.java:445)
2024-01-17 16:50:14     at clojure.lang.AFn.applyToHelper(AFn.java:160)
2024-01-17 16:50:14     at clojure.lang.RestFn.applyTo(RestFn.java:132)
2024-01-17 16:50:14     at clojure.core$apply.invokeStatic(core.clj:673)
2024-01-17 16:50:14     at clojure.core$apply.invoke(core.clj:662)
2024-01-17 16:50:14     at metabase.db.setup$fn__50124$fn__50134.doInvoke(setup.clj:56)
2024-01-17 16:50:14     at clojure.lang.RestFn.invoke(RestFn.java:445)
2024-01-17 16:50:14     at metabase.db.setup$fn__50162$_AMPERSAND_f__50163.invoke(setup.clj:148)
2024-01-17 16:50:14     at metabase.db.setup$fn__50162$fn__50169.invoke(setup.clj:142)
2024-01-17 16:50:14     at metabase.db.setup$fn__50172$_AMPERSAND_f__50173$fn__50176$fn__50177.invoke(setup.clj:166)
2024-01-17 16:50:14     at metabase.util.jvm$do_with_us_locale.invokeStatic(jvm.clj:239)
2024-01-17 16:50:14     at metabase.util.jvm$do_with_us_locale.invoke(jvm.clj:225)
2024-01-17 16:50:14     at metabase.db.setup$fn__50172$_AMPERSAND_f__50173$fn__50176.invoke(setup.clj:161)
2024-01-17 16:50:14     at metabase.db.setup$fn__50172$_AMPERSAND_f__50173.invoke(setup.clj:160)
2024-01-17 16:50:14     at metabase.db.setup$fn__50172$fn__50184.invoke(setup.clj:154)
2024-01-17 16:50:14     at metabase.db$setup_db_BANG_$fn__50193.invoke(db.clj:69)
2024-01-17 16:50:14     at metabase.db$setup_db_BANG_.invokeStatic(db.clj:64)
2024-01-17 16:50:14     at metabase.db$setup_db_BANG_.invoke(db.clj:55)
2024-01-17 16:50:14     at metabase.core$init_BANG__STAR_.invokeStatic(core.clj:113)
2024-01-17 16:50:14     at metabase.core$init_BANG__STAR_.invoke(core.clj:98)
2024-01-17 16:50:14     at metabase.core$init_BANG_.invokeStatic(core.clj:156)
2024-01-17 16:50:14     at metabase.core$init_BANG_.invoke(core.clj:151)
2024-01-17 16:50:14     at metabase.core$start_normally.invokeStatic(core.clj:168)
2024-01-17 16:50:14     at metabase.core$start_normally.invoke(core.clj:162)
2024-01-17 16:50:14     at metabase.core$entrypoint.invokeStatic(core.clj:201)
2024-01-17 16:50:14     at metabase.core$entrypoint.doInvoke(core.clj:195)
2024-01-17 16:50:14     at clojure.lang.RestFn.invoke(RestFn.java:397)
2024-01-17 16:50:14     at clojure.lang.AFn.applyToHelper(AFn.java:152)
2024-01-17 16:50:14     at clojure.lang.RestFn.applyTo(RestFn.java:132)
2024-01-17 16:50:14     at clojure.lang.Var.applyTo(Var.java:705)
2024-01-17 16:50:14     at clojure.core$apply.invokeStatic(core.clj:667)
2024-01-17 16:50:14     at clojure.core$apply.invoke(core.clj:662)
2024-01-17 16:50:14     at metabase.bootstrap$_main.invokeStatic(bootstrap.clj:31)
2024-01-17 16:50:14     at metabase.bootstrap$_main.doInvoke(bootstrap.clj:28)
2024-01-17 16:50:14     at clojure.lang.RestFn.invoke(RestFn.java:397)
2024-01-17 16:50:14     at clojure.lang.AFn.applyToHelper(AFn.java:152)
2024-01-17 16:50:14     at clojure.lang.RestFn.applyTo(RestFn.java:132)
2024-01-17 16:50:14     at metabase.bootstrap.main(Unknown Source)
2024-01-17 16:50:14 Caused by: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v00.00-000::qnkhuat:
2024-01-17 16:50:14      Reason: liquibase.exception.DatabaseException: ERROR: extension "citext" is not allow-listed for "azure_pg_admin" users in Azure Database for PostgreSQL
2024-01-17 16:50:14   Hint: to see the full allow list of extensions, please run: "show azure.extensions;" [Failed SQL: (0) --
2024-01-17 16:50:14 -- Name: citext; Type: EXTENSION; Schema: -; Owner: -
2024-01-17 16:50:14 --
2024-01-17 16:50:14 
2024-01-17 16:50:14 CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public]
2024-01-17 16:50:14     at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:123)
2024-01-17 16:50:14     at liquibase.command.core.AbstractUpdateCommandStep.lambda$run$0(AbstractUpdateCommandStep.java:102)
2024-01-17 16:50:14     at liquibase.Scope.lambda$child$0(Scope.java:194)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:203)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:193)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:172)
2024-01-17 16:50:14     at liquibase.command.core.AbstractUpdateCommandStep.run(AbstractUpdateCommandStep.java:99)
2024-01-17 16:50:14     at liquibase.command.CommandScope.execute(CommandScope.java:212)
2024-01-17 16:50:14     ... 53 more
2024-01-17 16:50:14 Caused by: liquibase.exception.MigrationFailedException: Migration failed for changeset migrations/001_update_migrations.yaml::v00.00-000::qnkhuat:
2024-01-17 16:50:14      Reason: liquibase.exception.DatabaseException: ERROR: extension "citext" is not allow-listed for "azure_pg_admin" users in Azure Database for PostgreSQL
2024-01-17 16:50:14   Hint: to see the full allow list of extensions, please run: "show azure.extensions;" [Failed SQL: (0) --
2024-01-17 16:50:14 -- Name: citext; Type: EXTENSION; Schema: -; Owner: -
2024-01-17 16:50:14 --
2024-01-17 16:50:14 
2024-01-17 16:50:14 CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public]
2024-01-17 16:50:14     at liquibase.changelog.ChangeSet.execute(ChangeSet.java:761)
2024-01-17 16:50:14     at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:61)
2024-01-17 16:50:14     at liquibase.changelog.ChangeLogIterator$2.lambda$null$0(ChangeLogIterator.java:111)
2024-01-17 16:50:14     at liquibase.Scope.lambda$child$0(Scope.java:194)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:203)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:193)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:172)
2024-01-17 16:50:14     at liquibase.changelog.ChangeLogIterator$2.lambda$run$1(ChangeLogIterator.java:111)
2024-01-17 16:50:14     at liquibase.Scope.lambda$child$0(Scope.java:194)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:203)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:193)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:172)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:260)
2024-01-17 16:50:14     at liquibase.changelog.ChangeLogIterator$2.run(ChangeLogIterator.java:94)
2024-01-17 16:50:14     at liquibase.Scope.lambda$child$0(Scope.java:194)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:203)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:193)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:172)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:260)
2024-01-17 16:50:14     at liquibase.Scope.child(Scope.java:264)
2024-01-17 16:50:14     at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:68)
2024-01-17 16:50:14     ... 60 more
2024-01-17 16:50:14 Caused by: liquibase.exception.DatabaseException: ERROR: extension "citext" is not allow-listed for "azure_pg_admin" users in Azure Database for PostgreSQL
2024-01-17 16:50:14   Hint: to see the full allow list of extensions, please run: "show azure.extensions;" [Failed SQL: (0) --
2024-01-17 16:50:14 -- Name: citext; Type: EXTENSION; Schema: -; Owner: -
2024-01-17 16:50:14 --
2024-01-17 16:50:14 
2024-01-17 16:50:14 CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public]
2024-01-17 16:50:14     at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:445)
2024-01-17 16:50:14     at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:77)
2024-01-17 16:50:14     at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:160)
2024-01-17 16:50:14     at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1287)
2024-01-17 16:50:14     at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1269)
2024-01-17 16:50:14     at liquibase.changelog.ChangeSet.execute(ChangeSet.java:718)
2024-01-17 16:50:14     ... 80 more
2024-01-17 16:50:14 Caused by: org.postgresql.util.PSQLException: ERROR: extension "citext" is not allow-listed for "azure_pg_admin" users in Azure Database for PostgreSQL
2024-01-17 16:50:14   Hint: to see the full allow list of extensions, please run: "show azure.extensions;"
2024-01-17 16:50:14     at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)
2024-01-17 16:50:14     at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401)
2024-01-17 16:50:14     at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:335)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:321)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:297)
2024-01-17 16:50:14     at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:292)
2024-01-17 16:50:14     at com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:75)
2024-01-17 16:50:14     at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:441)
2024-01-17 16:50:14     ... 85 more

Do you have any idea what happend here?

Luiggi · January 17, 2024, 9:26pm

Which version of Postgres are you using?

andresg · January 17, 2024, 9:46pm

Thanks for the quick response, I found the error, you have to activate some Azure permissions in the cloud to enable some Postgres extensions that were requested