Repository navigation
Migration from Keycloak 22.0.5 to Keycloak 24.0.5 #33249
Unanswered
atulchauhan01
asked this question in
Q&A
Replies: 2 comments 2 replies
|
What result do you get when running the following query? Because if you delete the result, it'll probably run fine. SELECT * FROM REALM WHERE id = 'D6HJ5fghBFDre8i8';By the way, Keycloak should be the only entity making changes to that database up to this point. If anything else was modifying it, the whole migration process will no longer work as intended. |
2 replies
|
Hi, we've experienced the same issue when migrating from 23 to 26 but only when we had batching enabled for migration: Without it, it worked well but it is very slow (takes ~45 minutes for 350 realms). |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are currently migrating from Keycloak version 22.0.5 to version 24.0.5. However, during the migration process, we encounter the following error:
The migration process attempts to insert data into the
realmtable, but it fails with a duplicate key error. We have reviewed the JPA changelog files for versions 23 and 24, but there don’t appear to be any changes related to therealmtable.This behaviour is quite unexpected, and we’re unsure why the migration process is trying this insert operation, or why it is failing if it is a necessary step of migration.
Logs:
We attempted to narrow down the issue and, following the advice found in multiple discussions on the forum to migrate one version at a time, we first upgraded to Keycloak version 23. The migration to version 23 was smooth, and we did not encounter any issues.
However, when we proceeded to migrate from Keycloak 23 to Keycloak 24, the same problem resurfaced. So essentially, we are facing the issue when upgrading to Keycloak 24, whether it’s from Keycloak 22 or Keycloak 23.
Has anyone else experienced this issue when upgrading to Keycloak 24 or any other version? Any insights or suggestions on how to resolve this would be greatly appreciated!
All reactions