Repository navigation
Replies: 3 comments 11 replies
|
For now we'll use |
|
I can indeed see that the hash is different than we have in our databases: https://github.com/keycloak/keycloak/blob/release/26.0/model/jpa/src/main/resources/META-INF/jpa-changelog-26.0.0.xml#L77 |
|
@Thijmen moved to a discussion because it was dealing with Docker, but now that I've looked at it more it doesn't seem related to Docker. Looking that the changelog you are referencing, the checksum was added in 26.0.5 and above with #34521 The likely sequence is that you had migrated to 26.0 prior to 26.0.5, liquibase created a checksum that was different than this one, and now that it's validating migrations with a later version like 26.0.8 you are getting these errors. @sguilhen @rmartinc or someone else from the storage team will need to weigh in here as well. |
Uh oh!
There was an error while loading. Please reload this page.
Before reporting an issue
Area
core
Describe the bug
Hi there,
So we've updated our own Dockerimage and this shows now when starting the container:
We're using
quay.io/keycloak/keycloak:26.0When I go to https://quay.io/repository/keycloak/keycloak?tab=tags&tag=latest I see that
26.0has been updated 18 hours ago. May it be related to this?Version
quay.io/keycloak/keycloak:26.0
Regression
Expected behavior
Keycloak container boots succesfully.
Actual behavior
Container shows error.
How to Reproduce?
I guess start a container with the same image version (and have an existing Docker-volume)
Anything else?
No response
All reactions