Error metabase.middelware :::: GET /api/dashboard 500 (14 ms) (7 DB calls)

OS : Ubuntu 16.04
The Old Metabase : 0.28.1
The New Metabase : 0.31.2

I want to do migration from the the old metabase to the more recent version. I successfully install the new metabase in different server, but pointing to the same exact database (Postgres) . But somehow the old metabase got this error

GET /api/database 500 (3 ms) (2 DB calls)
{:message "Assert failed: (is-permissions-set? permissions-set)",
 :type java.lang.AssertionError,
 :stacktrace
 ["models.permissions$set_has_partial_permissions_for_set_QMARK_.invokeStatic(permissions.clj:164)"
  "models.permissions$set_has_partial_permissions_for_set_QMARK_.invoke(permissions.clj:164)"
  "models.interface$make_perms_check_fn$_has_perms_QMARK___20061.invoke(interface.clj:140)"
  "models.interface$fn__20011$G__20004__20020.invoke(interface.clj:93)"
  "api.database$dbs_list.invokeStatic(database.clj:139)"
  "api.database$dbs_list.invoke(database.clj:138)"
  "api.database$fn__37262$fn__37263.invoke(database.clj:149)"
  "api.common.internal$do_with_caught_api_exceptions.invokeStatic(internal.clj:254)"
  "api.common.internal$do_with_caught_api_exceptions.invoke(internal.clj:249)"
  "api.database$fn__37262.invokeStatic(database.clj:144)"
  "api.database$fn__37262.invoke(database.clj:144)"
  "middleware$enforce_authentication$fn__33152.invoke(middleware.clj:123)"
  "api.routes$fn__46096.invokeStatic(routes.clj:65)"
  "api.routes$fn__46096.invoke(routes.clj:65)"
  "routes$fn__46856$fn__46857.doInvoke(routes.clj:106)"
  "routes$fn__46856.invokeStatic(routes.clj:101)"
  "routes$fn__46856.invoke(routes.clj:101)"
  "middleware$log_api_call$fn__33251$fn__33253.invoke(middleware.clj:342)"
  "middleware$log_api_call$fn__33251.invoke(middleware.clj:341)"
  "middleware$add_security_headers$fn__33201.invoke(middleware.clj:255)"
  "core$wrap_streamed_json_response$fn__47651.invoke(core.clj:66)"
  "middleware$bind_current_user$fn__33156.invoke(middleware.clj:144)"
  "middleware$maybe_set_site_url$fn__33205.invoke(middleware.clj:279)"]}

Another error

Error syncing fields for Table 178 'public.churntesting_ggi_session_detail': Output of parent-id->fields does not match schema:

Are you trying to connect the 2 versions to the same database? The schema will have changed as soon as the new version connected.

Yes, is there any documentation about the schema’s differences between version ?

All I know is that it won’t work

@dodolgarut
Like @AndrewMBaines says, you cannot use different versions on the same internal database, since the first one will likely change the schema.
Metabase added support for multiple instances in 0.30:
https://github.com/metabase/metabase/issues/2754
You can see all schema changes here:
https://github.com/metabase/metabase/blob/master/resources/migrations/000_migrations.yaml

1 Like